Add enhancement check in case bot account has no write access on repos #1988
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Zelin Hao zelinhao@amazon.com
Description
Add additional check when creating release tag after each release.
Old workflow used to fail immediately if bot account doesn't have write access on one specific repos. If it doesn't have write access on a number of repos, it will fail each time when the access issue happens.
This enhancement will store the repo names in a list and continue with other repos if the bot account doesn't have access on some repos. The entire job will still fail but provide a list of all the untagged repo names while all other tags created on the rest of them on the manifest.
Issues Resolved
#1860
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.