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.

Sign up for GitHub

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

Jump to bottom

feat: release on specific labels #119

Merged
merged 1 commit into from
Apr 30, 2024
Merged

feat: release on specific labels #119

merged 1 commit into from
Apr 30, 2024

Commits on Apr 30, 2024

  1. feat: release on specific labels 

    Related to github/github-ospo#105

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

Signed-off-by: jmeridth <[email protected]>
    @jmeridth
    jmeridth committed Apr 30, 2024
    Configuration menu
    Copy the full SHA
    45ea74f View commit details
    Browse the repository at this point in the history