Backlog

Module-Template 🔗  

This view lists issues. It pulls these issues from Github using Hugo GetRemote. It is looking for a repo in your org named Module-<module-name> where it expects issues to live. You can edit this of course.

It combines the repo name with the org api url set in hugo.toml to fetch the issues at that endpoint. That repo is the source of truth. This view just mirrors whatever is in there.

Organise your issues with labels, like ‘Week 1’ or ‘Week 2’ to filter them into the right section or sprint. Pass the label into the backlog_filter in the front matter to filter the issues.

The issues typically link to coursework stored in the Module-<module-name> repo, but they don’t have to.

Expand all

It doesn't look like there are any backlog items for this sprint - is that correct?

If you expected to see tasks but they aren't showing up you should check:

  • There is a GitHub issue in the appropriate repo with teh details of the task
  • The task's title, priority, and GitHub url were all added to backlog.json