build-slug-id-list.sh
Scans a directory of tracks and creates a track-slugs.yml
file.convert-to-dev-track.sh
Converts to a '-dev' version of a track.promote-track-changes.sh
Merges changes made in a '-dev' version of a track.PATH
environment variable:instruqt-development
.instruqt-development
, create a subdirectory called instruqt-tracks
.instruqt-tracks
subdirectory. instruqt-tracks
subdirectory are up-to-date with the latest content. You might do an instruqt track pull
in each track directory to make sure..github
directory into the instruqt-development
directory:https://github.com/instruqt/examples/tree/master/.github
and hit Enter.
↳ A ZIP file with the .github
directory is downloaded..github
and move the .github
directory into the instruqt-development
directory.
↳ The .github
directory contains actions and workflows that will run automatically when you push updates to GitHub and merge pull requests.instruqt-tracks
directory and generate a track-slugs.yml
file by running this script:track-slugs.yml
file looks something like this:instruqt-development\.github\dev-track-test.yml
in your code editor and enter your team slug into the ORGANIZATION-SLUG
property—for example: instruqt-development\.github\prod-track-test.yml
and edit the on
property to the following if needed:InstruqtDevelopment
.INSTRUQT_TOKEN
.instruqt-development
directory for Git:instruqt-development
directory.track-slugs.yml
file will be validated, tested, and pushed to production.instruqt-development
directory if needed.DEV -
prefix.my-dev-branch
.Development Track Test
workflow run.
↳ The workflow tests your track and shows a green checkmark when the tests are successful. Production Track Test
workflow run.
↳ The workflow tests your track and promotes your changes to the production track while preserving all your Instruqt track IDs.