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.

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

ci: improve backport PR title and body #420

Merged
merged 1 commit into from Apr 22, 2024
Merged

ci: improve backport PR title and body #420

merged 1 commit into from Apr 22, 2024

Conversation

apricote
Copy link
Member

The previous templates were not compatible with our usage:

  • The title was prefixed with [Backport release-1.x] which broke release-please
  • The body was empty besides the comment about backporting. By default we use the PR body as the commit message, so we should include the relevant details here.

@apricote apricote self-assigned this Apr 22, 2024
@apricote apricote requested a review from a team as a code owner April 22, 2024 09:41
Copy link

codecov bot commented Apr 22, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.43%. Comparing base (6c96d19) to head (86c1251).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #420   +/-   ##
=======================================
  Coverage   80.43%   80.43%           
=======================================
  Files          32       32           
  Lines        5756     5756           
=======================================
  Hits         4630     4630           
  Misses        718      718           
  Partials      408      408           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@jooola
Copy link
Member

jooola commented Apr 22, 2024

What about using a fork of tibdex/backport that include my PR tibdex/backport#109 and also embed the release-please commit override ?

The previous templates were not compatible with our usage:

- The title was prefixed with `[Backport release-1.x]` which broke
  `release-please`
- The body was empty besides the comment about backporting. By default
  we use the PR body as the commit message, so we should include the
  relevant details here.
@apricote
Copy link
Member Author

What about using a fork of tibdex/backport that include my PR tibdex/backport#109 and also embed the release-please commit override ?

Done!

@apricote apricote merged commit 2e44ada into main Apr 22, 2024
5 checks passed
@apricote apricote deleted the backport-config branch April 22, 2024 09:50
@apricote
Copy link
Member Author

Will mark this PR as backport to test the new templates.

@apricote apricote added the backport release-1.x Open PR against release-1.x with these changes after the PR is merged. label Apr 22, 2024
github-actions bot pushed a commit that referenced this pull request Apr 22, 2024
The previous templates were not compatible with our usage:

- The title was prefixed with `[Backport release-1.x]` which broke
`release-please`
- The body was empty besides the comment about backporting. By default
we use the PR body as the commit message, so we should include the
relevant details here.

(cherry picked from commit 2e44ada)
apricote added a commit that referenced this pull request Apr 22, 2024
The previous templates were not compatible with our usage:

- The title was prefixed with `[Backport release-1.x]` which broke
`release-please`
- The body was empty besides the comment about backporting. By default
we use the PR body as the commit message, so we should include the
relevant details here.

---
Backport 2e44ada from #420.

Co-authored-by: Julian Tölle <julian.toelle@hetzner-cloud.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport release-1.x Open PR against release-1.x with these changes after the PR is merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants