Closed makubacki closed 1 year ago
@kuqin12 and @os-d in the course of testing this earlier I exceeded the GitHub GraphQL API limit and had to come back to it. After further testing, I decided to take a different approach. Please let me know if you have any concerns.
@kuqin12 and @os-d in the course of testing this earlier I exceeded the GitHub GraphQL API limit and had to come back to it. After further testing, I decided to take a different approach. Please let me know if you have any concerns.
I think the new approach looks fine to me.
The
release-drafter
GitHub action has anexclude-contributors
configuration option that excludes usernames from the final contributors. This does not appear to work for dependabot.The
exclude-labels
configuration option does work. This change adds a new labeltype:dependabot
to dependabot PRs (via the dependabot config file) and uses theexclude-labels
option in therelease-drafter
config file to exclude those PRs from release notes.Submodules are currently updated by either
dependabot
or thesubmodule-release-updater
GitHub action local to mu_devops. Since submodules are recursive to repo consumers and to keep those consistently in the release notes, thetype:dependabot
label is not added to dependabot submodule updates keeping those updates in the release notes.