Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Split template and software repo

Open
#24 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, shell
Domain
ci-cd, devops

Research direction

Start with the linked GitHub Actions reusable-workflow documentation, then inspect the existing deploy and backup workflows in the template and software repositories. Define the repository boundary and workflow-calling arrangement, and verify that workflow updates ship after a template is used and that Django- or Next.js-specific templates remain possible.

Written by the indexing model from the issue text.

Description

GH workflows can access other workflows across repos; see also: https://docs.github.com/en/actions/how-tos/reuse-automations/reuse-workflows#calling-a-reusable-workflow

This would enable shipping updates to workflows ever after a template has been used.
Especially the deploy and backup workflows could be managed by the software repo.

This would also enable us to create more specific templates for common frameworks like Django or Next.js.

Dominant language
Shell
Stars
8
Forks
0
Avg merge
12h 28m
Merged PRs (30d)
15

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from codingjoe/the-box

All issues in codingjoe/the-box

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.