GothenburgBitFactory/timewarrior
1
0
Fork 0
mirror of https://github.com/GothenburgBitFactory/timewarrior.git synced 2025-06-26 10:54:28 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fix spelling

Browse source 
Signed-off-by: Thomas Lauf <thomas.lauf@tngtech.com>
This commit is contained in:
Thomas Lauf 2023-01-07 18:58:42 +01:00
parent ca5de02c56
commit 84c65f0324
3 changed files with 8 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

12
CONTRIBUTING.md
View file

@ -43,7 +43,7 @@ Review the source code, and point out inefficiencies, problems, unreadable funct
## Bug reports ## Bug reports
Before you submit a bug report, make sure you are using the latest version of Timewarrior. Before you submit a bug report, make sure you are using the latest version of Timewarrior.
Also please take your time and scan the current bug tickets on our [Github issue tracker](https://github.com/GothenburgBitFactory/timewarrior/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3Abug) whether your issue has already been reported. Also please take your time and scan the current bug tickets on our [GitHub issue tracker](https://github.com/GothenburgBitFactory/timewarrior/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3Abug) whether your issue has already been reported.
When you submit a bug report, be precise and put as much information into your bug report as possible. When you submit a bug report, be precise and put as much information into your bug report as possible.
You should at least provide You should at least provide
@ -64,7 +64,7 @@ An example:
## Feature requests ## Feature requests
As for bug reports, you should check our [Github issue tracker](https://github.com/GothenburgBitFactory/timewarrior/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3Aenhancement) whether your feature has already been requested. As for bug reports, you should check our [GitHub issue tracker](https://github.com/GothenburgBitFactory/timewarrior/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3Aenhancement) whether your feature has already been requested.
When you submit a feature request, provide a use case which captures the overall intention of your feature, not the technical implementation. When you submit a feature request, provide a use case which captures the overall intention of your feature, not the technical implementation.
@ -101,7 +101,7 @@ Consult the [documentation](https://timewarrior.net/docs/api.html) on how you ca
### Tests, Bug-fixes and Features ### Tests, Bug-fixes and Features
In general your contributions have to be associated with an issue on our [Github issue tracker](https://github.com/GothenburgBitFactory/timewarrior/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen). In general your contributions have to be associated with an issue on our [GitHub issue tracker](https://github.com/GothenburgBitFactory/timewarrior/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen).
See the sections above on how to submit bug reports and feature requests. See the sections above on how to submit bug reports and feature requests.
Code contributions are only accepted as pull-requests. Code contributions are only accepted as pull-requests.
@ -128,9 +128,9 @@ This is the branch where your changes must go.
The `master` branch always points to the latest release. The `master` branch always points to the latest release.
No development takes place here. No development takes place here.
To make a pull request you need to have a Github account. To make a pull request you need to have a GitHub account.
1. Fork the [Timewarrior repository](https://github.com/GothenburgBitFactory/timewarrior) on Github. 1. Fork the [Timewarrior repository](https://github.com/GothenburgBitFactory/timewarrior) on GitHub.
1. Checkout the development branch. 1. Checkout the development branch.
$ git checkout dev $ git checkout dev
@ -148,7 +148,7 @@ To make a pull request you need to have a Github account.
Furthermore, commits should be signed off according to the [DCO](DCO) (use `-s` / `--signoff` flag when commiting). Furthermore, commits should be signed off according to the [DCO](DCO) (use `-s` / `--signoff` flag when commiting).
1. Create the pull request on Github. 1. Create the pull request on GitHub.
## What happens next? ## What happens next?

2
ChangeLog
View file

@ -59,7 +59,7 @@
- #398 test: Thread.isAlive() -> Thread.is_alive() - #398 test: Thread.isAlive() -> Thread.is_alive()
(thanks to Shaun Ruffell) (thanks to Shaun Ruffell)
- #410 Replace roff man pages with asciidoctor - #410 Replace roff man pages with asciidoctor
- #411 Transfer platform testing from Travis CI to Github Actions - #411 Transfer platform testing from Travis CI to GitHub Actions
- #416 Internal error. Failed encode / decode check when doing undo - #416 Internal error. Failed encode / decode check when doing undo
(thanks to narudarurarasya, Shaun Ruffel) (thanks to narudarurarasya, Shaun Ruffel)
- #419 Links not preserved over linebreaks in man page - #419 Links not preserved over linebreaks in man page

2
DCO
View file

@ -38,7 +38,7 @@ using your real name (sorry, no pseudonyms or anonymous contributions.)
The DCO text can either be manually added to your commit body, or you can add either **-s** or **--signoff** to your usual git commit commands. The DCO text can either be manually added to your commit body, or you can add either **-s** or **--signoff** to your usual git commit commands.
If you forget to add the sign-off you can also amend a previous commit with the sign-off by running **git commit --amend -s**. If you forget to add the sign-off you can also amend a previous commit with the sign-off by running **git commit --amend -s**.
If you've pushed your changes to Github already you'll need to force push your branch after this with **git push -f**. If you've pushed your changes to GitHub already you'll need to force push your branch after this with **git push -f**.
#### Alternative Sign-Off Methods in rare cases #### Alternative Sign-Off Methods in rare cases