forked from dandi/dandi-infrastructure
-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
Please use the "duplicate issue" button in the bottom to create a new issue from this template
Steps
- Create new branch
sync-...fromapl-setup - Sync
masterwith (from)dandi/dandi-infrastructure:master- Using GitHub buttton on this repository's home page
- Open a pull request to merge
masterintosync-...mastercontains all of the dandi/dandi-infrastructure update- while
sync-...contains all of our EMBER updates
- Review changes
- Resolve merge conflicts
- I usually do this locally by merging
masterintosync-...and dealing with conflicts in VSCode. Because, we don't want to add any of our EMBER changes to themasterbranch. We wantmasterto always be "dandi-only" code
- I usually do this locally by merging
- PR closed
Now, sync-... contains all of the updates both from dandi-instructure and our fork!
- Open pull request to merge
sync-...intoapl-setupto update our infrastructure (sandbox + prod) in terraform - Review changes
- Merge PR
- Apply Terraform changes
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels