Shareable configuration
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 339
- Forks
- 93
- PR merge metrics
- No merged PRs in 30d
Description
Expected Behavior
Mergify should be able to be pointed to a configuration hosted somewhere else, using it as a base, similar to what, for instance Renovate does.
This is particularly handy when someone has many repositories needing the same (base) configuration.
Actual Behavior
As far as I know, the same configuration should get copied and pasted into every repository.
Proposal
These are some ideas of what it could look like, but better ways might be concocted.
# Imports the content of the URI, using it as a base
from: '<some URI>'
Alternatively:
# Includes rules from somewhere else, possibly with multiple sources.
import_pull_request_rules:
- '<some URI>'
- '<some other URI>'
import_queue_rules:
- '<some URI>'
- '<some other URI>'
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
The issue names no files, tests, or entry points; start by locating Mergify's configuration parsing and loading path. Clarify the supported URI and import behavior from the proposal, then define completion as allowing a repository to use hosted configuration or imported rules as a base.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100