Skip to content
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

Documentation: broken links (correct md link syntax) in contributing.md #5301

Merged
merged 1 commit into from Apr 13, 2023
Merged

Documentation: broken links (correct md link syntax) in contributing.md #5301

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 4 additions & 4 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,13 +7,13 @@ The [Algorand GitHub Organization](https://github.com/algorand) has all of our o
## Non-code Contributions

While contributions come in many forms, this document is focused on code. For other types of involvement, see the following:
* [Reporting issues and features requests.](go-algorand-issues)
* [Security vulnerability disclosures.](security-disclosure)
* [Documentation improvements.](algorand-docs)
* [Reporting issues and features requests.][go-algorand-issues]
* [Security vulnerability disclosures.][security-disclosure]
* [Documentation improvements.][algorand-docs]

## Contribution Model

All changes to `go-algorand` are made through the same process: a pull request targeting the `master` branch. This goes for internal and external contributions. To familiarize yourself with the process we recommend that you review the current open pull requests, and the GitHub documentation for [creating a pull request from a fork](gh-pr-process).
All changes to `go-algorand` are made through the same process: a pull request targeting the `master` branch. This goes for internal and external contributions. To familiarize yourself with the process we recommend that you review the current open pull requests, and the GitHub documentation for [creating a pull request from a fork][gh-pr-process].

Note: some of our other projects are using gitflow, for these the process is the same but you will target pull requests against the `develop` branch.

Expand Down