Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
hg-git
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Terraform modules
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
mercurial
hg-git
Commits
7c7e296f
Commit
7c7e296f
authored
10 years ago
by
durin42
Browse files
Options
Downloads
Patches
Plain Diff
Add a file with contribution guidelines.
parent
13d42d32
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
CONTRIBUTING
+25
-0
25 additions, 0 deletions
CONTRIBUTING
with
25 additions
and
0 deletions
CONTRIBUTING
0 → 100644
+
25
−
0
View file @
7c7e296f
The short version:
* Patches should have a good summary line for first line of commit message
* Patches should be sent to the Google Group[0]
even look at those.
* Patch needs to do exactly one thing
* testsuite passes
The longer version:
We use a variant of Mercurial's own contribution
system. http://mercurial.selenic.com/wiki/ContributingChanges contains
their full guidelines. Key differences are (by rule number):
1. For hg-git, I'm not rigied about the "topic: a few words" format
for the first line, but I do insist on a sensible summary as the
first line of your commit
2. We don't require use of issueNNN for bug fixes (we have no robot)
3. Use the hg-git google group
10. We use mostly pep8 style. The current codebase is a mess, but new
code should be basically pep8.
0: Pull requests are generally not noticed more than once every few
months. If you do a pull request, I'm still going to expect you to
have a clean history, and to be willing to rework history so it's
clean before I push the "merge" button.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment