You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[biocswirl] [biocterm] [dev] [doc] Hackseq second README check
Tasks
[x] Include names & git usernames of ALL your team members
Depending on your project status:
Standing prototype:
[x] README targets end users
[x] Should have clear installation/usage instructions
Ongoing work:
[ ] README targets potential developers
[ ] Should have clear descriptions of the different files/scripts, their relation to each other, and how they should fit together
Other:
[x] README targets people interested in hackseq in general
[x] Should have a description of the task distribution, the work done, and the experience overall
Due 3PM, get feedback by 5PM
Resources
Tag can be
biocswirl(related to course material)
biocterm (interface changes)
dev (developers only)
file (changes to file and folder structuring)
rpkg (r package/usethis and CRAN documentation changes)
feat (new feature)
fix (bug fix)
refactor (refactoring code)
style (formatting, missing semi colons, etc; no code change)
doc (changes to documentation)
test (adding or refactoring tests; no production code change)
version (version bump/new release; no production code change)
dbg (Changes in debugging code/frameworks; no production code change)
license (Edits regarding licensing; no production code change)
hack (Temporary fix to make things move forward; please avoid it)
WIP (Work In Progress; for intermediate commits to keep patches reasonably sized)
The text was updated successfully, but these errors were encountered:
[biocswirl] [biocterm] [dev] [doc] Hackseq second README check
Tasks
[x] Include names & git usernames of ALL your team members
Depending on your project status:
Standing prototype:
[x] README targets end users
[x] Should have clear installation/usage instructions
Ongoing work:
[ ] README targets potential developers
[ ] Should have clear descriptions of the different files/scripts, their relation to each other, and how they should fit together
Other:
[x] README targets people interested in hackseq in general
[x] Should have a description of the task distribution, the work done, and the experience overall
Due 3PM, get feedback by 5PM
Resources
Tag can be
The text was updated successfully, but these errors were encountered: