Use environment-specific URLs instead of
...hard-coded ones
This commit is contained in:
parent
6ca5704c21
commit
1b05e63a20
76 changed files with 91 additions and 91 deletions
|
@ -14,7 +14,7 @@ After reading this, my question is, "Should you, or do you need to, create branc
|
|||
|
||||
These days, I use trunk-based development as much as possible, so I hardly ever create new branches, whether working on a project myself or with a team.
|
||||
|
||||
[I used to use Git Flow](https://www.oliverdavies.uk/presentations/git-flow) and create branches for every new feature and bug fix, but I remember, whilst demonstrating two work-in-progress features to a client, switching between the different branches caused my local site to break. Whilst it wasn’t a major issue, it wouldn't have seemed professional.
|
||||
[I used to use Git Flow]({{site.url}}/presentations/git-flow) and create branches for every new feature and bug fix, but I remember, whilst demonstrating two work-in-progress features to a client, switching between the different branches caused my local site to break. Whilst it wasn’t a major issue, it wouldn't have seemed professional.
|
||||
|
||||
In a team environment, feature branches are intended to keep different changes and different people's work separate.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue