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
Now that blog versioning has been added to content layer, figure out the desired workflow.
Should all modifications to mdx file increment version?
How should auto-linking work? Ideally find a flow where versioning is abstracted away so no need for unnecessary builds, local/remote branches going out of sync, or basically anything manual needs to happen. (it's ok if local linking is fudged if it's documented)
Should rendered version text box point to commit or PR on GH? Both? Conditional?
Now that blog versioning has been added to content layer, figure out the desired workflow.
Should all modifications to mdx file increment version?
How should auto-linking work? Ideally find a flow where versioning is abstracted away so no need for unnecessary builds, local/remote branches going out of sync, or basically anything manual needs to happen. (it's ok if local linking is fudged if it's documented)
Should rendered version text box point to commit or PR on GH? Both? Conditional?
What should major/minor revisions mean for this?
Autoincrement versions
Autolink versions to diff on github
Build checks