-
-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Fix Various Grammar Issues and Adjust Unnatural Wording #2737
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -38,8 +38,8 @@ and answer the questions so we can understand and reproduce the | |
problematic behavior. | ||
|
||
To show us that the issue you are having is in Gitea itself, please | ||
write clear, concise instructions so we can reproduce the behavior | ||
(even if it seems obvious). The more detailed and specific you are, | ||
write clear, concise instructions so we can reproduce the behavior— | ||
even if it seems obvious. The more detailed and specific you are, | ||
the faster we can fix the issue. Check out [How to Report Bugs | ||
Effectively](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html). | ||
|
||
|
@@ -48,15 +48,10 @@ getting free help. | |
|
||
## Discuss your design | ||
|
||
The project welcomes submissions but please let everyone know what | ||
you're working on if you want to change or add something to the Gitea | ||
repositories. | ||
|
||
Before starting to write something new for the Gitea project, please [file | ||
an issue](https://github.com/go-gitea/gitea/issues/new). Significant | ||
changes must go through the [change proposal | ||
process](https://github.com/go-gitea/proposals) before they can be | ||
accepted. | ||
The project welcomes submissions. If you want to change or add something, | ||
please let everyone know what you're working on—[file an issue](https://github.com/go-gitea/gitea/issues/new)! | ||
Significant changes must go through the [change proposal process](https://github.com/go-gitea/proposals) | ||
before they can be accepted. | ||
|
||
This process gives everyone a chance to validate the design, helps | ||
prevent duplication of effort, and ensures that the idea fits inside | ||
|
@@ -72,9 +67,9 @@ and keep the compatibility on upgrade. To make sure you are | |
running the test suite exactly like we do, you should install | ||
the CLI for [Drone CI](https://github.com/drone/drone), as | ||
we are using the server for continous testing, following [these | ||
instructions](http://readme.drone.io/usage/getting-started-cli). After | ||
that you can simply call `drone exec` within your working directory and | ||
it will try to run the test suite locally. | ||
instructions](http://readme.drone.io/usage/getting-started-cli). After that, | ||
you can simply call `drone exec` within your working directory and it will try | ||
to run the test suite locally. | ||
|
||
## Vendoring | ||
|
||
|
@@ -109,13 +104,13 @@ An exception are the tools to build the CSS and images. | |
|
||
## Code review | ||
|
||
Changes to Gitea must be reviewed before they are accepted, no matter who | ||
makes the change even if it is an owner or a maintainer. We use GitHub's | ||
pull request workflow to do that and we also use [LGTM](http://lgtm.co) | ||
Changes to Gitea must be reviewed before they are accepted—no matter who | ||
makes the change, even if they are an owner or a maintainer. We use GitHub's | ||
pull request workflow to do that. And, we also use [LGTM](http://lgtm.co) | ||
to ensure every PR is reviewed by at least 2 maintainers. | ||
|
||
Please try to make your pull request easy to review for us. | ||
Please read the [How to get faster PR reviews](https://github.com/kubernetes/community/blob/master/contributors/devel/faster_reviews.md) guide, | ||
Please try to make your pull request easy to review for us. And, please read | ||
the *[How to get faster PR reviews](https://github.com/kubernetes/community/blob/master/contributors/devel/faster_reviews.md)* guide; | ||
it has lots of useful tips for any project you may want to contribute. | ||
Some of the key points: | ||
|
||
|
@@ -146,7 +141,7 @@ import ( | |
) | ||
``` | ||
|
||
## Sign your work | ||
## Sign-off your work | ||
|
||
The sign-off is a simple line at the end of the explanation for the | ||
patch. Your signature certifies that you wrote the patch or otherwise | ||
|
@@ -158,9 +153,9 @@ to every git commit message: | |
Signed-off-by: Joe Smith <[email protected]> | ||
``` | ||
|
||
Please use your real name, we really dislike pseudonyms or anonymous | ||
Please use your real name; we really dislike pseudonyms or anonymous | ||
contributions. We are in the open-source world without secrets. If you | ||
set your `user.name` and `user.email` git configs, you can sign your | ||
set your `user.name` and `user.email` git configs, you can sign-off your | ||
commit automatically with `git commit -s`. | ||
|
||
## Release Cycle | ||
|
@@ -170,18 +165,20 @@ on, finishing, and issuing releases. The overall goal is to make a | |
minor release every two months, which breaks down into one month of | ||
general development followed by one month of testing and polishing | ||
known as the release freeze. All the feature pull requests should be | ||
merged in the first month of one release period and during the frozen | ||
period a corresponding release branch is open for fix backported from | ||
master. Release candidate are made along this period for user testing to | ||
merged in the first month of one release period. And, during the frozen | ||
period, a corresponding release branch is open for fixes backported from | ||
master. Release candidates are made during this period for user testing to | ||
obtain a final version that is maintained in this branch. A release is | ||
maintained by issuing patch releases to only correct critical problems | ||
such as crashes or security issues. | ||
|
||
The current release cycle is aligned to start on December 25 to February | ||
24, next is February 25 to April 24, and etc. On this cycle, we also | ||
maybe publish the previous release minor version. For example, the | ||
current release version is v1.1, but we maybe also publish v1.0.2. When | ||
we publish v1.2, then we will stop publish v1.0.3. | ||
Major release cycles are bimonthly. They always begin on the 25th and end on | ||
the 24th (i.e., the 25th of December to February 24th). | ||
|
||
During a development cycle, we may also publish any necessary minor releases | ||
for the previous version. For example, if the latest, published release is | ||
v1.2, then minor changes for the previous release—e.g., v1.1.0 -> v1.1.1—are | ||
still possible. | ||
|
||
## Maintainers | ||
|
||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -33,17 +33,17 @@ This project has been | |
## Notes | ||
|
||
1. **YOU MUST READ THE [CONTRIBUTORS GUIDE](CONTRIBUTING.md) BEFORE STARTING TO WORK ON A PULL REQUEST.** | ||
2. If you found a vulnerability in the project, please write privately to **[email protected]**. Thanks! | ||
2. If you have found a vulnerability in the project, please write privately to **[email protected]**. Thanks! | ||
3. If you're interested in using our APIs, we have experimental support with [documentation](https://godoc.org/code.gitea.io/sdk/gitea). | ||
|
||
## Docs | ||
|
||
For more information and instructions about how to install Gitea | ||
please look at our [documentation](https://docs.gitea.io/en-us/). | ||
If you cannot find some specific information, then head over to | ||
our [Discord server](https://discord.gg/NsatcWJ) | ||
or [Matrix room](https://matrix.to/#/#gitea:matrix.org) to chat with us | ||
or use the [forum](https://discourse.gitea.io/). | ||
For more information and instructions about how to install Gitea, please look | ||
at our [documentation](https://docs.gitea.io/en-us/). If you have questions | ||
that are not covered by the documentation, you can get in contact with us on | ||
our [Discord server](https://discord.gg/NsatcWJ), | ||
[Matrix room](https://matrix.to/#/#gitea:matrix.org), | ||
or [forum](https://discourse.gitea.io/)! | ||
|
||
## Contributing | ||
|
||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Signed commits and Sign-offs are different things. https://help.github.com/articles/signing-commits-using-gpg/
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am aware; that's why I modified that section. It seems to me that it is referring to sign-offs and not actual PGP signings. Here is the full section for context. It never mentions PGP keys. But, it does give an example of using the standard git sign-off.
Maybe I missed something, though 😉
EDIT: Ah, yeah, it also uses the lowercase
-s
flag—which is used for a sign-off and not a PGP signed commit (-S
). Maybe that section header should also be changed from "Sign your work" so that it is less confusing?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ooh nvm, I though about
git commit -S
😅