search

NDCLab / lab-devOps

NDCLab mgmt and operations
GNU Affero General Public License v3.0
0 stars 0 forks source link

gh-forking template repos #55

Closed jessb0t closed 2 years ago

jessb0t commented 3 years ago

DONE Defined:

Determine whether the forking of a template repo:

F-said commented 3 years ago

@jessb0t Switched template to repo to preserve branching once forked. Satisfies the above conditions.

jessb0t commented 3 years ago

@F-said: Thank you! I will continue the conversation about templates (particularly so I can set up the "study" one) at our next devOps meeting. Closing this issue now. 🙂

jessb0t commented 3 years ago

Plan A: use the built-in template feature for our template-tool and template-project repos. Failure point: if we create main and dev branches with the appropriate branch protection rules, we can never merge from dev to main on repos created from the template.

Plan B: create regular repos for the templates and have users fork those repos to create new repos. Failure point: you cannot fork from NDCLab to NDCLab.

Plan C: have users clone and rename the template repos, create empty shell repos on NDCLab, and push those back to GitHub Failure point: the cloned repos drop branch protection rules.

Plan D: create template repos in GB's personal GH, have users fork to NDCLab org Failure point: the forked repos drop branch protection rules.

jessb0t commented 3 years ago

@F-said:

  1. Turn template-tool repo back into a GitHub "template."
  2. Remove dev branch from this template.
  3. Create how-to on github-templates.md for creating dev branch, setting branch protection rules (incl. no deletion of dev), and auto-deletion of HEAD branches after merge.
  4. Check whether there is an easy GitHub Actions option to make this any easier?
jessb0t commented 2 years ago

Closing this issue now that template repos are set up and process established!