forked from nf-core/sarek
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request nf-core#557 from MaxUlysse/CleanUp
Cleaning up
- Loading branch information
Showing
12 changed files
with
20 additions
and
126 deletions.
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,25 +1,25 @@ | ||
# CAW Contributing Guidelines | ||
# Sarek Contributing Guidelines | ||
|
||
Hi there! Many thanks for taking an interest in improving CAW. | ||
Hi there! Many thanks for taking an interest in improving Sarek. | ||
|
||
We try to manage the required tasks for CAW using GitHub issues, you probably came to this page when creating one. Please use the prefilled template to save time. | ||
We try to manage the required tasks for Sarek using GitHub issues, you probably came to this page when creating one. Please use the prefilled template to save time. | ||
|
||
However, don't be put off by this template - other more general issues and suggestions are welcome! Contributions to the code are even more welcome ;) | ||
|
||
> If you need help using CAW then the best place to go is the Gitter chatroom where you can ask us questions directly: https://gitter.im/SciLifeLab/CAW | ||
> If you need help using Sarek then the best place to go is the Gitter chatroom where you can ask us questions directly: https://gitter.im/SciLifeLab/Sarek | ||
## Contribution workflow | ||
If you'd like to write some code for CAW, the standard workflow | ||
If you'd like to write some code for Sarek, the standard workflow | ||
is as follows: | ||
|
||
1. Check that there isn't already an issue about your idea in the | ||
[CAW issues](https://github.com/SciLifeLab/CAW/issues) to avoid | ||
[Sarek issues](https://github.com/SciLifeLab/Sarek/issues) to avoid | ||
duplicating work. | ||
* Feel free to add a new issue here for the same reason. | ||
2. Fork the CAW repository to your GitHub account | ||
2. Fork the Sarek repository to your GitHub account | ||
3. Make the necessary changes / additions within your forked repository | ||
4. Submit a Pull Request against the master branch and wait for the code to be reviewed and merged. | ||
|
||
If you're not used to this workflow with git, you can start with some [basic docs from GitHub](https://help.github.com/articles/fork-a-repo/) or even their [excellent interactive tutorial](https://try.github.io/). | ||
|
||
For further information/help, please consult the [CAW documentation](https://github.com/SciLifeLab/CAW#documentation) and don't hesitate to get in touch on [Gitter](https://gitter.im/SciLifeLab/CAW) or contact us: maxime.garcia@scilifelab.se, szilveszter.juhos@scilifelab.se | ||
For further information/help, please consult the [Sarek documentation](https://github.com/SciLifeLab/Sarek#documentation) and don't hesitate to get in touch on [Gitter](https://gitter.im/SciLifeLab/Sarek) or contact us: maxime.garcia@scilifelab.se, szilveszter.juhos@scilifelab.se |
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
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,5 +1,4 @@ | ||
Annotation/ | ||
data/chr17_testdata/ | ||
Preprocessing/ | ||
References/ | ||
Reports/ | ||
|
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
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
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
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
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
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
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
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
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