Skip to content

Update or delete out-of-date branches from repo #57

@broncio123

Description

@broncio123

Hi @stephenwiggins @Shibabrat

I have some proposed changes and questions. Please, give me your thoughts whenever possible.

PROPOSAL

  • Update or delete branches that lead to subfolders in content with updated subfolders from develop.

I can see that having these branches is useful to do version control of files from an individual subfolder only - so that people don't have to clone a repo with all the book files, which can be merged into develop, and release to reflect changes on the book.
Q: How did you guys created these branches that point to subfolders only? using submodules or subtrees? @Shibabrat @rgmeseguer @vkrajnak

  • Delete master or update as a branch from the latest commit of release. Then, link Netlify build for chemicalreactions.io site to master instead of release.

  • Delete all hotfix branches and any other branch used to perform changes to input files.

These branches are just going to accumulate and they don't seem to be useful anymore, as the main input files are corrected in develop and release. Any thoughts not to delete these will be considered.

Best
@broncio123

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestquestionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions