Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to publish rust docs only for the base template of an assigment #793

Open
nuke-web3 opened this issue Jul 27, 2023 · 1 comment
Open
Labels
content-tips Ideas for crafting great content. maybe-someday Dreaming of what we can and should do

Comments

@nuke-web3
Copy link

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).

@nuke-web3 nuke-web3 added maybe-someday Dreaming of what we can and should do content-tips Ideas for crafting great content. labels Jul 27, 2023
@nuke-web3
Copy link
Author

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.

https://stackoverflow.com/questions/14365946/create-a-branch-alias

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content-tips Ideas for crafting great content. maybe-someday Dreaming of what we can and should do
Projects
None yet
Development

No branches or pull requests

1 participant