You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We don't want to use the master copy of these repos, as that will be divergent over time, where the cohort template will remain static once we are done, and students can have all resources locked as how they got them for each tag of this content repo (all associated materials are tagged or forked for them is the goal).
The text was updated successfully, but these errors were encountered:
Perhaps we could make a branch that isn't main but is a direct parallel - if possible an alias that we don't need to independently remember to update alongside main with a workflow to build and publish... so .github/ is only present for the alias and a job building on that branch, not main. So students don't get the CI job automatically added to their assignment's fork.
Having a per-cohort version of the rust docs for each assignment is a nice to have thing, for example for https://github.com/Polkadot-Blockchain-Academy/pba-ucb-frameles-node-template where they need to build locally to view rather than just browse these.
We don't want to use the
master
copy of these repos, as that will be divergent over time, where the cohort template will remain static once we are done, and students can have all resources locked as how they got them for each tag of this content repo (all associated materials are tagged or forked for them is the goal).The text was updated successfully, but these errors were encountered: