Data Browser
- Viewing Site
Sector 23 Code Bank
Logged in as:
Guest
Similar Topics...
NET 5 HttpPost Model null if too large and other issues
Change Bing Maps InfoBox height to auto (v7
NET - Create Custom Event for Class/UserControl
Things to Look for in a Code Review
Sector 23 Code Bank
Angular ui-date respond to date change
Change CSS class name dynamically using javascript
Reporting Services - The Item '/Data Sources' Does Not Exist - Lost Administrator rights to SSRS
Should you use var in C
SQL Server Query to get Latest Backup Date
XML Files are too large
C:\windows\temp filling up with large cab files
Wordfeud vs Wordyx - feature comparison
Change Datatype of column
Change PrintArea in Excel using EPPlus
Testing SQL Code without cache - SQL Server
Page-Break-After results in extra page in Chrome
Angular ui-calendar change view
NET Change ImageUrl of HyperLink using JavaScript
Angular JS - hide code while rendering
Best Practices - C# .NET Naming Conventions
How to Create a Bar Graph / 3D Pie Chart in PowerPoint using .NET OpenXML API
NET Download Large Zip File
Set width of anchor (a) in CSS
The Sector 23 Code Bank
TFS/Git Branching Strategy
Simplest is
best
. Minimizing merges will
result
in fewer complicated bugs/inadvertently
lost
code
.
There
should
be one master/main branch representing the
latest
code
.
Small/iterative
change
s
should
be made in master.
Large
feature
s can be made in
a
one-off
feature
branch and merged into master as soon as possible (when stable).
The more everyone is in master the better, as it minimize situations where
feature
branches diverge and the later inventible merge becomes
a
nightmare.
When ready for
a
release,
create
a
branch for
that
release.
Create
a
branch for each
new
major release.
Delete
when no longer
needed
(e.g. 3 releases out of
date
).
More here:
https://docs.microsoft.com/en-us/azure/devops/repos/git/git-branching-guidance?view=azure-devops
Created By: amos
9/28/2020 9:14:37 AM
Updated:
9/28/2020 9:15:45 AM