Skip to content

Template Practice Repositories

Use template repositories when learners need their own safe copy of a project.

A template repository lets each learner create a new repository from the same starting files. They can branch, commit, push, open pull requests, and merge without changing the course site or another learner’s work.

Use one active template for the first course run. Add more only when the course needs a different practice context.

Template repositoryStatusPurposeExample learner tasks
git-basics-sql-practiceReadySQL analysis workflowedit a query, add notes, update a data dictionary, open a PR

Future template ideas, if the course expands:

  • git-basics-docs-practice — documentation-only workflow: fix a typo, improve instructions, respond to PR feedback.
  • git-basics-data-dictionary-practice — metadata workflow: add a field definition, review naming, update source notes.

The first course run should use git-basics-sql-practice. It is realistic enough for analysts and statisticians without requiring live database credentials.

git-basics-sql-practice/
├── README.md
├── queries/
│ ├── 01-count-visits.sql
│ └── 02-enrollment-summary.sql
├── data-dictionary/
│ └── fields.md
├── analysis-notes/
│ └── visit-count-notes.md
└── troubleshooting/
└── common-issues.md

Keep the repository small. The goal is Git practice, not SQL mastery.

  • Small SQL files that can be read without a database connection.
  • Data dictionary markdown files with realistic field names.
  • Analysis notes where learners can write short observations.
  • A README.md with expected workflow and branch naming examples.
  • No connection strings, credentials, private hostnames, or real client data.

Each learner creates their own repository from the template:

  1. Open BigInformatics/git-basics-sql-practice.
  2. Select Use this template.
  3. Create a repository under their own account or training organization.
  4. Clone their new repository.
  5. Complete the course exercises in that copy.

Use the git-basics- prefix for every practice template so repositories appear together in GitHub search and organization lists.

Good examples:

git-basics-sql-practice
git-basics-docs-practice
git-basics-data-dictionary-practice

Avoid vague names such as practice-repo or training-files.