Skip to content

docs: fix empty repo link and typo in CONTRIBUTING #2825

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.

Sign up for GitHub

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
murchandamus merged 2 commits into from
Jul 21, 2026
Merged

docs: fix empty repo link and typo in CONTRIBUTING #2825

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
04089e7
docs: fix empty repo link and typo in CONTRIBUTING
Bartok9 Jul 21, 2026
31c6769
docs: shorten repo link text per reviewer suggestion
Bartok9 Jul 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,14 +62,14 @@ standardized:
- Using a commit message similar to `news70: add Japanese translation` helps
keep translations easily visible in the commit log
- Testing your translation
- Follow the instuctions in the [README.md](https://github.com/bitcoinops/bitcoinops.github.io/blob/master/README.md)
- Follow the instructions in the [README.md](https://github.com/bitcoinops/bitcoinops.github.io/blob/master/README.md)
- `make preview` to view the local website and review
- `make production` to run additional checks (link checking, linting, etc)
- For the page you have translated, ensure that the language code link shows
up on the `en` language variant
- Check that the page renders properly
- Create a pull request to the
[https://github.com/bitcoinops/bitcoinops.github.io]() repository
[bitcoinops/bitcoinops.github.io](https://github.com/bitcoinops/bitcoinops.github.io) repository
- One newsletter per PR allows for easier review
- Allowing edits from maintainers permits maintainers to make additional
commits to your PR branch
Expand Down