Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(bot comparison): add Dependabot as GitHub Action #28921

Conversation

HonkingGoose
Copy link
Collaborator

Changes

  • Add new way of running Dependabot: as a GitHub Actions workflow
  • Link to the Blog post
  • Link to the official GitHub Docs page

Context

Not closing any issue with this PR.

Quote from the GitHub Blog:

Starting today, administrators using Github.com accounts can enable their repositories and/or organizations to run Dependabot updates jobs as a GitHub Actions workflow using both hosted and self-hosted runners. Running Dependabot does not count towards GitHub Actions minutes–meaning that using Dependabot continues to be free for everyone.

Documentation (please check one with an [x])

  • I have updated the documentation, or
  • No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

  • Code inspection only, or
  • Newly added/modified unit tests, or
  • No unit tests but ran on a real repository, or
  • Both unit tests + ran on a real repository

@rarkins rarkins added this pull request to the merge queue May 8, 2024
Merged via the queue into renovatebot:main with commit 54ba9af May 8, 2024
35 checks passed
@HonkingGoose HonkingGoose deleted the docs/dependabot-as-github-action-workflow branch May 8, 2024 09:01
@renovate-release
Copy link
Collaborator

🎉 This PR is included in version 37.351.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants