Closed jmeridth closed 4 months ago
Related to https://github.com/github/github-ospo/issues/105
Only generate a release if our semver related labels (breaking, enhancement, fix) or the release label are present on a merged pull request.
breaking
enhancement
fix
release
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.
vuln
npm run lint
npm run test
bug
documentation
infrastructure
maintenance
Related to https://github.com/github/github-ospo/issues/105
Pull Request
Proposed Changes
Only generate a release if our semver related labels (
breaking
,enhancement
,fix
) or therelease
label are present 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.vuln
andrelease
labels to repositoryReadiness Checklist
Author/Contributor
npm run lint
and fix any linting issues that have been introducednpm run test
and run testsReviewer
bug
,documentation
,enhancement
,infrastructure
,maintenance
, orbreaking