mirror of
https://github.com/git/git.git
synced 2026-01-22 08:27:53 +00:00
Merge 'readme' into HEAD
Add a README.md for GitHub goodness. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
This commit is contained in:
Johannes Schindelin
63
.github/ISSUE_TEMPLATE.md
vendored
Normal file
63
.github/ISSUE_TEMPLATE.md
vendored
Normal file
@@ -0,0 +1,63 @@
|
||||
- [ ] I was not able to find an [open](https://github.com/git-for-windows/git/issues?q=is%3Aopen) or [closed](https://github.com/git-for-windows/git/issues?q=is%3Aclosed) issue matching what I'm seeing
|
||||
|
||||
### Setup
|
||||
|
||||
- Which version of Git for Windows are you using? Is it 32-bit or 64-bit?
|
||||
|
||||
```
|
||||
$ git --version --build-options
|
||||
|
||||
** insert your machine's response here **
|
||||
```
|
||||
|
||||
- Which version of Windows are you running? Vista, 7, 8, 10? Is it 32-bit or 64-bit?
|
||||
|
||||
```
|
||||
$ cmd.exe /c ver
|
||||
|
||||
** insert your machine's response here **
|
||||
```
|
||||
|
||||
- What options did you set as part of the installation? Or did you choose the
|
||||
defaults?
|
||||
|
||||
```
|
||||
# One of the following:
|
||||
> type "C:\Program Files\Git\etc\install-options.txt"
|
||||
> type "C:\Program Files (x86)\Git\etc\install-options.txt"
|
||||
> type "%USERPROFILE%\AppData\Local\Programs\Git\etc\install-options.txt"
|
||||
$ cat /etc/install-options.txt
|
||||
|
||||
** insert your machine's response here **
|
||||
```
|
||||
|
||||
- Any other interesting things about your environment that might be related
|
||||
to the issue you're seeing?
|
||||
|
||||
** insert your response here **
|
||||
|
||||
### Details
|
||||
|
||||
- Which terminal/shell are you running Git from? e.g Bash/CMD/PowerShell/other
|
||||
|
||||
** insert your response here **
|
||||
|
||||
- What commands did you run to trigger this issue? If you can provide a
|
||||
[Minimal, Complete, and Verifiable example](http://stackoverflow.com/help/mcve)
|
||||
this will help us understand the issue.
|
||||
|
||||
```
|
||||
** insert your commands here **
|
||||
```
|
||||
- What did you expect to occur after running these commands?
|
||||
|
||||
** insert here **
|
||||
|
||||
- What actually happened instead?
|
||||
|
||||
** insert here **
|
||||
|
||||
- If the problem was occurring with a specific repository, can you provide the
|
||||
URL to that repository to help us with testing?
|
||||
|
||||
** insert URL here **
|
||||
19
.github/PULL_REQUEST_TEMPLATE.md
vendored
19
.github/PULL_REQUEST_TEMPLATE.md
vendored
@@ -1,7 +1,18 @@
|
||||
Thanks for taking the time to contribute to Git! Please be advised that the
|
||||
Git community does not use github.com for their contributions. Instead, we use
|
||||
a mailing list (git@vger.kernel.org) for code submissions, code reviews, and
|
||||
bug reports. Nevertheless, you can use submitGit to conveniently send your Pull
|
||||
Thanks for taking the time to contribute to Git!
|
||||
|
||||
Those seeking to contribute to the Git for Windows fork should see
|
||||
http://gitforwindows.org/#contribute on how to contribute Windows specific enhancements.
|
||||
|
||||
If your contribution is for the core Git functions and documentation
|
||||
please be aware that the Git community does not use the github.com issues
|
||||
or pull request mechanism for their contributions.
|
||||
|
||||
Instead, we use the Git mailing list (git@vger.kernel.org) for code and
|
||||
documenatation submissions, code reviews, and bug reports. The
|
||||
mailing list is plain text only (anything with HTML is sent directly
|
||||
to the spam folder).
|
||||
|
||||
Nevertheless, you can use submitGit to conveniently send your Pull
|
||||
Requests commits to our mailing list.
|
||||
|
||||
Please read the "guidelines for contributing" linked above!
|
||||
|
||||
76
CONTRIBUTING.md
Normal file
76
CONTRIBUTING.md
Normal file
@@ -0,0 +1,76 @@
|
||||
# Git for Windows Code of Conduct
|
||||
|
||||
This code of conduct outlines our expectations for participants within the **Git for Windows** community, as well as steps to reporting unacceptable behavior. We are committed to providing a welcoming and inspiring community for all and expect our code of conduct to be honored. Anyone who violates this code of conduct may be banned from the community.
|
||||
|
||||
## Our Pledge
|
||||
|
||||
In the interest of fostering an open and welcoming environment, we as
|
||||
contributors and maintainers pledge to making participation in our project and
|
||||
our community a harassment-free experience for everyone, regardless of age, body
|
||||
size, disability, ethnicity, gender identity and expression, level of experience,
|
||||
nationality, personal appearance, race, religion, or sexual identity and
|
||||
orientation.
|
||||
|
||||
## Our Standards
|
||||
|
||||
Examples of behavior that contributes to creating a positive environment
|
||||
include:
|
||||
|
||||
* Using welcoming and inclusive language
|
||||
* Being respectful of differing viewpoints and experiences
|
||||
* Gracefully accepting constructive criticism
|
||||
* Focusing on what is best for the community
|
||||
* Showing empathy towards other community members
|
||||
|
||||
Examples of unacceptable behavior by participants include:
|
||||
|
||||
* The use of sexualized language or imagery and unwelcome sexual attention or
|
||||
advances
|
||||
* Trolling, insulting/derogatory comments, and personal or political attacks
|
||||
* Public or private harassment
|
||||
* Publishing others' private information, such as a physical or electronic
|
||||
address, without explicit permission
|
||||
* Other conduct which could reasonably be considered inappropriate in a
|
||||
professional setting
|
||||
|
||||
## Our Responsibilities
|
||||
|
||||
Project maintainers are responsible for clarifying the standards of acceptable
|
||||
behavior and are expected to take appropriate and fair corrective action in
|
||||
response to any instances of unacceptable behavior.
|
||||
|
||||
Project maintainers have the right and responsibility to remove, edit, or
|
||||
reject comments, commits, code, wiki edits, issues, and other contributions
|
||||
that are not aligned to this Code of Conduct, or to ban temporarily or
|
||||
permanently any contributor for other behaviors that they deem inappropriate,
|
||||
threatening, offensive, or harmful.
|
||||
|
||||
## Scope
|
||||
|
||||
This Code of Conduct applies both within project spaces and in public spaces
|
||||
when an individual is representing the project or its community. Examples of
|
||||
representing a project or community include using an official project e-mail
|
||||
address, posting via an official social media account, or acting as an appointed
|
||||
representative at an online or offline event. Representation of a project may be
|
||||
further defined and clarified by project maintainers.
|
||||
|
||||
## Enforcement
|
||||
|
||||
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
||||
reported by contacting the project team at **johannes.schindelin@gmx.de**. All
|
||||
complaints will be reviewed and investigated and will result in a response that
|
||||
is deemed necessary and appropriate to the circumstances. The project team is
|
||||
obligated to maintain confidentiality with regard to the reporter of an incident.
|
||||
Further details of specific enforcement policies may be posted separately.
|
||||
|
||||
Project maintainers who do not follow or enforce the Code of Conduct in good
|
||||
faith may face temporary or permanent repercussions as determined by other
|
||||
members of the project's leadership.
|
||||
|
||||
## Attribution
|
||||
|
||||
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
|
||||
available at [http://contributor-covenant.org/version/1/4][version]
|
||||
|
||||
[homepage]: http://contributor-covenant.org
|
||||
[version]: http://contributor-covenant.org/version/1/4/
|
||||
19
README.md
19
README.md
@@ -1,3 +1,19 @@
|
||||
Git for Windows
|
||||
===============
|
||||
|
||||
[](https://gitter.im/git-for-windows/git?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
|
||||
|
||||
This is [Git for Windows](http://git-for-windows.github.io/), the Windows port
|
||||
of [Git](http://git-scm.com/).
|
||||
|
||||
The Git for Windows project is run using a [governance
|
||||
model](http://git-for-windows.github.io/governance-model.html). If you
|
||||
encounter problems, you can report them as [GitHub
|
||||
issues](https://github.com/git-for-windows/git/issues), discuss them on Git
|
||||
for Windows' [Google Group](http://groups.google.com/group/git-for-windows),
|
||||
and [contribute bug
|
||||
fixes](https://github.com/git-for-windows/git/wiki/How-to-participate).
|
||||
|
||||
Git - fast, scalable, distributed revision control system
|
||||
=========================================================
|
||||
|
||||
@@ -27,7 +43,7 @@ CVS users may also want to read [Documentation/gitcvs-migration.txt][]
|
||||
(`man gitcvs-migration` or `git help cvs-migration` if git is
|
||||
installed).
|
||||
|
||||
The user discussion and development of Git take place on the Git
|
||||
The user discussion and development of core Git take place on the Git
|
||||
mailing list -- everyone is welcome to post bug reports, feature
|
||||
requests, comments and patches to git@vger.kernel.org (read
|
||||
[Documentation/SubmittingPatches][] for instructions on patch submission).
|
||||
@@ -35,6 +51,7 @@ To subscribe to the list, send an email with just "subscribe git" in
|
||||
the body to majordomo@vger.kernel.org. The mailing list archives are
|
||||
available at <https://public-inbox.org/git/>,
|
||||
<http://marc.info/?l=git> and other archival sites.
|
||||
The core git mailing list is plain text (no HTML!).
|
||||
|
||||
The maintainer frequently sends the "What's cooking" reports that
|
||||
list the current status of various development topics to the mailing
|
||||
|
||||
Reference in New Issue
Block a user