generated from AustralianBioCommons/guide-template
-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
29 additions
and
1 deletion.
There are no files selected for viewing
This file contains 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 |
---|---|---|
@@ -1,8 +1,36 @@ | ||
--- | ||
title: Contributing | ||
description: | ||
--- | ||
|
||
## Creating your own How-to Guide | ||
|
||
{% include callout.html type="important" content="Want to create your own How-to Guide? See [this guide](https://australianbiocommons.github.io/how-to-guide-template/) for more information." %} | ||
|
||
|
||
## Adding a How-to Guide to the Hub | ||
|
||
More information will be available soon. | ||
|
||
|
||
## Editing the How-to Hub | ||
|
||
### GitHub issues | ||
|
||
If you think something should be added, or if you find an error, bug or mistake, please [create an issue](https://github.com/AustralianBioCommons/how-to-hub/issues) detailing the problem. We will do our best to fix the issue as soon as possible. You can also create an issue by clicking the `!` symbol next to the title on any of the pages. | ||
|
||
|
||
### Pull Request | ||
|
||
If you want to edit content on this site, please do the following: | ||
|
||
1. Please let us know via GitHub [issues](https://github.com/AustralianBioCommons/how-to-hub/issues). | ||
2. Create your own fork of this GitHub repository. | ||
3. In your fork, create a branch with a concise name, that reflects its contents (e.g. `add/how-to-login-galaxy`). | ||
4. Make sure you update [`CONTRIBUTORS.yml`](_data/CONTRIBUTORS.yml). | ||
5. Create and commit the edits to your new branch. | ||
6. Open a GitHub Pull Request (PR) on this repository for your branch, concisely providing context for your additions. | ||
7. Follow-up on any feedback from the repository maintainers. | ||
8. Once ready, the maintainers will merge the changes and deploy the new content. | ||
|
||
|
||
## Thanks for contributing! |