Skip to content

Repo housekeeping #218

Open
Open
@petecooper

Description

@petecooper

As a precursor to #212, we need to address the multiple-branch setup of this repo and – ideally – pare it back to a single branch.

For legacy reasons, we used master when the pages were hosted on GitHub Pages. We use self-hosted for the self-hosted docs site which runs atop a bodged Jekyll instance. As #212 outlines, we can save resources & sanity by using a hosted docs service with proper search across all browsers etc.

Mercifully, there isn't a vast amount of difference between the two branches, though a clean PR cannot currently be raised. At the moment, there are around 10 to 20 files that are different across the two branches, so it's not a significant bum ache to pick through and make the changes manually (if necessary).

Proposal:

  • decide on the new branch name (main fits the bill and is suitably platform-agnostic)
  • decide on branch merge direction
  • decide on which current branch is to be renamed
  • merge branch diffs
  • bin the redundant branch
  • update contribution docs

Tagging for feedback: @Bloke @bloatware @philwareham

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions