Skip to content

Adapt website deployment pipeline to create multi-branch sites #20

New issue
New issue
Closed
Closed
Adapt website deployment pipeline to create multi-branch sites#20

Description

@NeuroShepherd
NeuroShepherd
opened on Feb 28, 2025

That is, every branch receives its own extension or address so that people can always see the development branches live online (but not have them listed as the main website)

Activity

  1. NeuroShepherd commented on Feb 28, 2025

    @NeuroShepherd
    NeuroShepherd
    on Feb 28, 2025
    MemberAuthor

    Notes:

    • Every branch needs to be checked out on each deployment
    • Only the branch that was edited needs to be re-rendered?
    • The content for each branch should be served at lmu-osc.github.io/website-address/BRANCH/
  2. lmu-osc
    locked and limited conversation to collaborators on Apr 2, 2026
  3. NeuroShepherd
    converted this issue into a discussion #37 on Apr 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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