You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 26, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 26, 2024. It is now read-only.
Just a general comment - Is there a reason the workflow is "submit a PR against live", and then live gets merged into master? It would be much easier to do it the other way around.
This actually creates extra steps for people submitting pull requests. By default, GitHub will setup a PR against master, even if you write changes against live. Having the workflow the way it is causes extra steps (that are easy to miss) when doing pull requests.
Master is the experimental branch for us currently, where everything resides. live is the branch that fetches public content that is live on MSDN. You could issue PRs against master, but that means we will still have to propagate changes to live to make sure that those are public.
At the end of the day, it's not a big deal - I do cross-syncs for both branches, so your content will go to live regardless of where you submit it. The general guideline is just to make sure that your content is in production faster 😄
Activity
dend commentedon May 31, 2016
Master is the experimental branch for us currently, where everything resides.
liveis the branch that fetches public content that is live on MSDN. You could issue PRs againstmaster, but that means we will still have to propagate changes toliveto make sure that those are public.smoothdeveloper commentedon Jun 30, 2016
Could we somehow setup the default branch in github to
live?I think this will fix the issue of
masterbeing picked by default when submitting a PR (which is what I mistakenly did on #195).ReedCopsey commentedon Jun 30, 2016
Client programs will always default to
master- so if you use github for windows, sourcetree, etc - you'll get master.dend commentedon Jul 1, 2016
At the end of the day, it's not a big deal - I do cross-syncs for both branches, so your content will go to
liveregardless of where you submit it. The general guideline is just to make sure that your content is in production faster 😄