-
Notifications
You must be signed in to change notification settings - Fork 35
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.
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
Proof of concept for release-please in biocommons.seqrepo #104
Milestone
Comments
Closed
holtgrewe
added a commit
to holtgrewe/biocommons.seqrepo
that referenced
this issue
May 4, 2023
Release-As: 0.6.6
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
github-actions
bot
added
the
stale
Issue is stale and subject to automatic closing
label
Sep 18, 2023
This issue was closed because it has been stalled for 7 days with no activity. |
reece
added
stale closed
Issue was closed automatically due to inactivity
and removed
stale closed
Issue was closed automatically due to inactivity
labels
Nov 27, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
release-please is a useful tool for automating release and changelog generation.
Example Projects
Prerequisites / Requirements
These things have to be
fix:
for fixes,feat:
for new features,ci:
for CI changes,build:
for build system changes,docs:
for documentation.ci: introducing release-please (#123)
.Needed Changes
.github/pull_request_template.md
PR template (cf snakemake's).CHANGELOG.md
filemain
branch to require a PR.github/workflows/conventional-prs.yml
to enforce conventional commit PRs, (cf. snakemake's).github/workflows/release-please.yml
to create Git tags, create GitHub releases, and publish to pypi (cf. snakemake's)Release Please Workflow
conventional-commits
workflowrelease-please
is triggered on each merge tomain
and will create and update a PR that updates the changelog (could also update the version in a setup.py file etc.) snakemake examplefix
will bump the patch version, afeat
will bump the minor version, any breaking change, e.g.,fix!
, orfeat!
will bump the major versionRelease-As: major.minor.patch
"footer" in the commit messagerelease-please
recognizes the merge to themain
tag and willThe text was updated successfully, but these errors were encountered: