Only generate a release and new action container images if our semver related labels (breaking, enhancement, fix) or the release label are used on a merged pull request.
Changed from push (merge) on main branch to release generation happening when a pull_request is merged to main branch.
This gives us access to the pull requests labels without having to make API cals.
Currently we'd still need to label a pull request with release if it is a dependabot or manual pull request related to a CVE or security fix.
[x] update CONTRIBUTING.md with new release information
[x] manually add vuln and release labels to repository
Readiness Checklist
Author/Contributor
[x] If documentation is needed for this change, has that been included in this pull request
[x] run make lint and fix any issues that you have introduced
[x] run make test and ensure you have test coverage for the lines you are introducing
Reviewer
[x] Label as either bug, documentation, enhancement, infrastructure, maintenance or breaking
Related to https://github.com/github/github-ospo/issues/105
Closes #59 Closes #60
Pull Request
Proposed Changes
Only generate a release and new action container images if our semver related labels (
breaking,enhancement,fix) or thereleaselabel are used on a merged pull request.Changed from push (merge) on main branch to release generation happening when a pull_request is merged to main branch.
This gives us access to the pull requests labels without having to make API cals.
Currently we'd still need to label a pull request with
releaseif it is a dependabot or manual pull request related to a CVE or security fix.vulnandreleaselabels to repositoryReadiness Checklist
Author/Contributor
make lintand fix any issues that you have introducedmake testand ensure you have test coverage for the lines you are introducingReviewer
bug,documentation,enhancement,infrastructure,maintenanceorbreaking