Sync Fork (Nov. 10 Week)

[NEStock]

Steps

• Create new branch sync-... from apl-setup
• Sync master with (from) dandi/dandi-infrastructure:master
  • Using GitHub buttton on this repository's home page
• Open a pull request to merge master into sync-...
  • master contains 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 master into sync-... and dealing with conflicts in VSCode. Because, we don't want to add any of our EMBER changes to the master branch. We want master to always be "dandi-only" code
• PR closed

Now, sync-... contains all of the updates both from dandi-instructure and our fork!

• Open pull request to merge sync-... into apl-setup to update our infrastructure (sandbox + prod) in terraform
• Extra Step for this Issue: Merge Set environment vars to set vendor-specific dandi-schema used by the DANDI instance #47 into sync-... branch.
  • this MR contains "EMBER-ifying" changes related to the changes from dandi
• Review changes
• Merge PR