Contents
What do you put in version control?
So what you should put in version control system? At least: Source code files. Scripts and other files you need to build software….
- Generated files.
- Build artifacts.
- IDE specific configuration files.
- Binary documentation files.
- Pre-compiled and source code of 3rd party dependencies.
- All other binary content.
How is code versioning controlled?
Version control, also known as source control, is the practice of tracking and managing changes to software code. Version control systems are software tools that help software teams manage changes to source code over time.
What is version control and why you should use it?
(Distributed) Git is a version control system, its open source and Distributed, designed to manage project speedy and efficient. In the Distributed framework, all developers have their local copies of files on the local repository, and when they push or comment the changes are stored at local repo first.
What should be stored in version control repository?
Binary documentation files. While storing documentation, such as pdfs or excel sheets, in the repository might make sense it does not actually bring any more value than you can rollback to specific version. You cannot diff the changes and see what has been changed and when.
How are Word documents stored in version control?
My company stores Word documents in SVN, and accesses them via TortoiseSVN. Tortoise uses Word’s built in change tracking function to show you a “diff” of two revisions. This works really well, but requires Windows and Word. You could probably get this working with git too.
How to treat the stored procedure in source control?
Treat the copy of the stored procedure in source control as the current version. It is your source code. Check it out, edit it, test it, install it, and check it back in. The next time it has to be changed, follow the same procedure. Just as an application requires a build and deploy process, so should the stored procedures.