`@openedx-community-bot` should merge with original commit message(s)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4
- Forks
- 33
- Avg merge
- 3d 54m
- Merged PRs (30d)
- 2
Description
@openedx-community-bot merge was used to merge this PR. The bot use the "Squash & Merge" strategy, dropped Maria's original commit message, and replaced it with the PR description (which included noise from the PR template): https://github.com/openedx/edx-platform/commit/a11ad35061e33041247d03d573e1ba0c32abd9ed
I think it would be better to do either a "Rebase & Merge" or a "Merge with Merge Commit", which would preserve the author's original commit messages and avoid copying in noise from the PR description. We currently lint commit messages, so it would make sense to use them.
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
The issue points to the @openedx-community-bot merge command, PR #30570, and commit a11ad35061e33041247d03d573e1ba0c32abd9ed. Start by locating the implementation or workflow entry point for that command and inspect how its merge strategy and commit message are selected. Done means merging preserves the author's original commit message(s) without replacing them with PR-template noise.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100