rebase workflow: create automated reports of branch drift
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 16
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 1
Description
Once a day, we'd like a report on
* Commits that are in `DMS/development` but not in `DMS/LP`
* Commits that are in `DMS/LP` but not in `mistserver/catalyst`
This will help us decide how frequently we need to rebase.
Contributor guide
No contributing guide indexed for this repository
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
No implementation file, test, or entry point is identified. Start by locating the repository's existing rebase or scheduled-workflow automation, then trace how branch comparisons are performed. Done means a daily report lists commits present in DMS/development but not DMS/LP, and commits present in DMS/LP but not mistserver/catalyst.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- devops, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100