Add git Dev Branch

The goal of this post is to:

  • Create a dev branch in git quickly to manage dev code before release
  • Establish main branch as the system update branch
Update to the latest:
git fetch origin

If you already created and pushed dev from main, just do:
git checkout dev

If not yet created, do this instead:
git checkout -b dev origin/main
git push -u origin dev

Now you’re on dev. Add your changes, commit, and push:
git add .
git commit -m "Start development on feature XYZ"
git push

Assumptions
  • Code already exists in the main branch
  • The main branch is already set up for releases, i.e. when code is pushed up
  • Pull requests are done in addition to the instructions above, which start the live releases
Stop tracking specific files.  For example, web.config should not be tracked.  To remove it but keep it on your local machine, do this:
git rm --cached web.config
git commit -m "Stop tracking web.config"


Other popular notes

Popular posts from this blog

SharePoint PowerShell Quick Guide

If you manage an online SharePoint tenant you will run into a lot of situations where PowerShell will be the surest way to accomplish your tasks. Permanently deleting a site via PowerShell Remove-SPOSite -Identity https://site.sharepoint.com Managing Hub Sites 2,000 hub sites per tenant A modern SharePoint site can be promoted to a Hub site As a team site As a communications site Global navigation added automatically Configure who is allowed to add sites to the hub Can also configure an approval workflow Hub site can be registered in the admin center Admins can choose who can associate sites with hub - Users, Security Groups, Office 365 Groups Hub site can be registed with PowerShell (to make it a hub site) Register-SPOHubSite -Site https://site.sharepoint.com/sites/hubsite -Principals $null To associate other sites to a hub Unregistering a hubsite disconnects it from the hub Unregister-SPOHubSite     -Identity https://sites.sharepoint.com/sites/an-existing-associated-site In ...
Read more

Dependency Injection in .NET

Here are some noteworthy takeaways from a course on Dependency Injection in .NET Core. DI Container Basics A container isn't a requirement but simplifies management of dependencies Services are registered at start up and resolve at runtime when they are required Container creates and disposes of instances while maintaining them for a specific lifetime Two primary interfaces for dependency injection in the .NET container IServicesCollection  - registers and configures a service IServiceProvider  - provides a mechanism for resolving a service at runtime Apply dependency via the constructor Register all services with the container Understand the service lifetimes Scoped Transient Singleton Identifying Dependencies to Register in the Container First, locate the  new  keyword usage. Is it the instance a dependency?  If a class instantiates another class whose methods are used, it's a dependency. Repeat the above approach throughout your app code (there should be code...
Read more

Git Guide

A few handy commands in one handy place. Updating .gitignore and enforcing it When you want to ignore additional files or folders, you have to update your . gitignore . After you make the additions or changes, you have to remove the cached files from the local repository, add them back, commit again to the local and push to the remote repositories: git rm -r --cached . git add . git commit -m "Ignore list update" To push the locally committed changes back to your remote repo: git push PowerShell script to sync with git This is a handy script I keep on my desktop (or an easy to find document folder) which I launch whenever I work with documents outside of a coding tool that need to be quickly pushed to Git. Write-Host 'Pushing changes to Git for my app!'; $dir = "C:\Users\username\source\repos\reponame\" Set-Location $dir Write-Output ''; Write-Output 'Adding locally...' git add . Write-Output ''; Write-Output "Committing locally....
Read more