An open API service indexing awesome lists of open source software.

https://github.com/virtool/workflow-create-sample

A workflow for creating Virtool samples
https://github.com/virtool/workflow-create-sample

virtool workflow

Last synced: 4 months ago
JSON representation

A workflow for creating Virtool samples

Awesome Lists containing this project

README

          

# workflow-create-sample

A workflow for creating Virtool samples.

## Steps

1. Run FastQC on the FASTQ data files.
2. Upload read files to the Virtool server.
3. Upload quality data to the Virtool server and finalize the sample.

## Contributing

### Commits

All commits must follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0) specification.

These standardized commit messages are used to automatically publish releases using [`semantic-release`](https://semantic-release.gitbook.io/semantic-release)
after commits are merged to `main` from successful PRs.

**Example**

```text
feat: add API support for assigning labels to existing samples
```

Descriptive bodies and footers are required where necessary to describe the impact of the commit. Use bullets where appropriate.

Additional Requirements
1. **Write in the imperative**. For example, _"fix bug"_, not _"fixed bug"_ or _"fixes bug"_.
2. **Don't refer to issues or code reviews**. For example, don't write something like this: _"make style changes requested in review"_.
Instead, _"update styles to improve accessibility"_.
3. **Commits are not your personal journal**. For example, don't write something like this: _"got server running again"_
or _"oops. fixed my code smell"_.

From Tim Pope: [A Note About Git Commit Messages](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)