digitalbazaar / digitalbazaar/pyld
Merge rules?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 683
- Forks
- 138
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 15
Description
To speed up merge process, we might develop an automatically enforced rule for merges. For instance:
- If the PR is not a draft,
- If CI on the PR is green,
- If the PR is approved by at least one maintainer,
- If the PR's branch is up to date against
master, - And the PR hasn't been updated for a week,
then it merges automatically. What do you guys think?
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
No implementation files, tests, or entry points are named. First clarify whether this automation is wanted and define the exact merge conditions, then identify the repository's CI or release configuration and verify that each condition is enforced before merging.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100