Remove release notes noise for backport releases
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 161
- Forks
- 141
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 138
Description
Patch Ert releases typically contains backports, for which the PR is automatically created.
The autogenerated release notes then end up containing noise, as in:
## What's Changed
### Other Changes
* [Backport version-16.0] Wrong number of Parameters when using Design Matrix by @scout-team-app[bot] in https://github.com/equinor/ert/pull/12265
where both strings "[Backport version-16.0]" and "by @scout-team-app]bot]" should be removed.
If not possible to remove during generation of the release notes, an action can be written to edit it.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how autogenerated release notes are produced for Patch Ert releases, using backport PR #12265 as the concrete example. Determine whether generation or a GitHub Action owns the text; done means the release notes omit both the "[Backport version-16.0]" prefix and the scout-team-app bot attribution without removing useful information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100