adding a CONTRIBUTING.md file - #868
Amrit-raj50 wants to merge 8 commits into
Conversation
|
@chriscool @sivaraam — Could you take a look at this when you get |
| @@ -0,0 +1,144 @@ | |||
| # Contributing to Git Developer Pages | |||
|
|
|||
| Thank you for your interest in contributing to [git.github.io](https://git.github.io) — the community website for Git development, home to the [Git Rev News newsletter](https://git.github.io/rev_news/), [Hacking Git](https://git.github.io/Hacking-Git/), and mentoring program information. | |||
There was a problem hiding this comment.
Please avoid long lines like this. Instead please split them at around 72 characters.
Also please avoid — characters. It looks too much AI generated.
| --- | ||
|
|
||
| ## Ways to Contribute | ||
|
|
There was a problem hiding this comment.
Please add an introduction sentence, like "In general we accept all kind of contributions to all the pages on this website, but here are some suggestions along with a few guidelines:"
|
|
||
| ## Ways to Contribute | ||
|
|
||
| - Fix typos, broken links, or outdated information |
| ## Ways to Contribute | ||
|
|
||
| - Fix typos, broken links, or outdated information | ||
| - Improve or add pages under `links/`, `rev_news/`, or other sections |
There was a problem hiding this comment.
I am not sure listing those directories make sense. I think it would make more sense to list the section on the website instead.
|
|
||
| - Fix typos, broken links, or outdated information | ||
| - Improve or add pages under `links/`, `rev_news/`, or other sections | ||
| - Add entries to the Git Rev News newsletter |
There was a problem hiding this comment.
It's not clear what "entries" means here. I think this should be more detailed. It should say what could be added in which section, how to find the upcoming edition where things can be added, and so on.
| - Fix typos, broken links, or outdated information | ||
| - Improve or add pages under `links/`, `rev_news/`, or other sections | ||
| - Add entries to the Git Rev News newsletter | ||
| - Improve site infrastructure (CSS, JavaScript, Jekyll layouts/plugins) |
There was a problem hiding this comment.
For any big improvement, people should look at existing issues and if needed create a new one before starting to work.
| git checkout -b my-fix | ||
| ``` | ||
| 4. **Make your changes**, following the [Writing Guidelines](#writing-guidelines) below. | ||
| 5. **Test locally** by [running the site](#running-the-site-locally) and verifying your changes look correct. |
There was a problem hiding this comment.
It's not necessary to test their changes locally when contributing to a Git Rev News edition.
|
@Amrit-raj50 I have left a number of comments. Thanks. |
|
I will raise the new PR for this after thrusday |
|
|
||
| - Fix typos, broken links, or outdated information across the site | ||
| (except for already published editions of Git Rev News, which are | ||
| kept as historical archives). |
There was a problem hiding this comment.
If possible open a Pull Request (PR) to submit your changes.
| (except for already published editions of Git Rev News, which are | ||
| kept as historical archives). | ||
| - Improve or add content to sections of the website such as the | ||
| Links page, Mentoring pages, or general documentation. |
There was a problem hiding this comment.
Here also, they might want to open a PR for this.
| plugins). Before starting work on major improvements, please check | ||
| existing issues and open a new issue for discussion first. | ||
| - Participate in community discussions by sharing opinions on open | ||
| issues or reviewing open Pull Requests. |
There was a problem hiding this comment.
It would be nice to have links to our open Issues and PRs.
| newsletter (see [below](#git-rev-news-newsletter)). | ||
| - Improve site infrastructure (CSS, JavaScript, Jekyll layouts, or | ||
| plugins). Before starting work on major improvements, please check | ||
| existing issues and open a new issue for discussion first. |
There was a problem hiding this comment.
It would be nice to have links to our open Issues.
| below. | ||
| 5. **Test locally** if needed by [running the site](#running-the-site-locally) | ||
| and verifying your changes look correct. (Note: this is not required | ||
| for newsletter contributions.) |
There was a problem hiding this comment.
It's also not required for small things like typofixes.
|
|
||
| Note: Running the site locally is helpful when working on layouts, | ||
| styles, or general pages, but it is **not required** when submitting | ||
| content for Git Rev News editions. |
There was a problem hiding this comment.
Not required also when sending typofixes or similar small changes.
| ### How to Contribute Content | ||
|
|
||
| Each upcoming edition is prepared in advance as a Markdown file under | ||
| `_posts/` (e.g. `_posts/YYYY-MM-DD-edition-XXX.markdown`). |
There was a problem hiding this comment.
Before being published, an edition is prepared under rev_news/drafts/, for example right now edition 139 is at: https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-139.md
But when an edition is published, its file is moved under _posts/ and renamed, for example: edition 138 is at: https://github.com/git/git.github.io/blob/master/_posts/2026-08-31-edition-138.markdown
|
|
||
| You can contribute in several ways: | ||
| - **Share entries in the edition issue:** A dedicated GitHub Issue is | ||
| opened for every upcoming edition (titled e.g. "Git Rev News Edition |
There was a problem hiding this comment.
The title is actually "Any comment about upcoming Git Rev News edition XXX" where XXX is the edition number, for example see: #860
| XXX"). You can comment directly on that issue with links, articles, | ||
| tools, or news you would like included. | ||
| - **Submit a Pull Request:** Add your entry directly to the draft file | ||
| under `_posts/` for the upcoming edition. Common entries include: |
There was a problem hiding this comment.
the draft file is not under _posts/, but rather under rev_news/drafts/
|
Thanks @Amrit-raj50, it's looking much better. I have commented on a few things that could still be improved though. |
This PR adds a CONTRIBUTING.md file to the repository.
GitHub automatically surfaces this file to anyone who opens a new
issue or pull request, helping new contributors understand how to
participate before they submit anything.
The file covers:
All information is based on the existing README.md and repository
conventions — nothing new is introduced, just consolidated in one
place for contributor discoverability.
Closes/Relates to: (add issue number if one exists)
issue : #864