nextcloud / nextcloud/backportbot
Inform about backport policy
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 14
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Adjust backport bot message to
- add info when backport should be done:
- TBD
- ask developer if they still think that backport is needed, else cancel/remove 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
The issue does not name files, tests, or an entry point. Start by locating where the backport bot constructs its messages, then clarify the missing backport-timing policy before changing behavior. Done means the message explains when a backport should happen and asks whether to cancel it when it is no longer needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100