- Document used to outline a development problem and a proposed solution
- Separate space for testing and developing code. Keeps bugs and issues isolated from production code.
- Systems to handle tracking and saving of code changes over time.
- Version control software (VCS) for managing code repositories as well as hosting said repositories.
- Prep changes for a commit. This allows you to pick and choose changes for a given commit.
- A snapshot of your repository at a given time. Like a save point.
- Move any commits/changes to a remote repository.
- Transition code from a remote repository to a local instance, be it Docker, GitHub, or any other remote repository. Allows others to utilize your pushed changes.
- Incorporate changes made on one branch into another, usually from a development branch into the main branch.
- Involves processes such as git fetch, pull, and push that keeps local and remote branches in concordance with one another.
- Publishing involves the committing and pushing of changes to a remote repository.
- Copies a remote repository into a directory on a local instance. This includes the ability to view branches and previous commits.
- Testing that the code changes functions correctly in likely scenarios.
- Ensure software meets very specific criteria like a previously defined benchmark
- Frequent contribution of code to a central repository from which automates builds and tests are run.
- The approval by end-users that the software meets needs and expectations.
- A deployment of a fixed software version that does not recieve changes regularly.
- A versioning scheme that reflects the severity of changes made to a codebase.
- A bundle of related computational resources that are required for certain pieces of software to function.
- Allows for ease of installation/update of software packages.
- Handle the execution and operation of workflow code within a standardized framework for reproducibility.
- The script that is executed by a workflow engine.
- Software that interpretes and executes workflow script.
- The order in which data can enter and exit a data structure, specifically Nextflow Channels.