MeltanoLabs / MeltanoLabs/Meta
Document Merge Etiquette
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
We may eventually want to create an adapted version of PR / Github etiquette for MeltanoLabs, just a thought. Could borrow from here but may have some differences: https://handbook.meltano.com/engineering/#responsibility-to-merge
As suggested by @aaronsteers in this PR comment we should also document merge etiquette for MeltanoLabs.
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
Start by reading the linked Meltano engineering handbook section on responsibility to merge and the referenced PR comment. The issue does not name a target file or format; done would mean agreeing on and adding adapted MeltanoLabs merge etiquette to the Meta repository.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100