Hi!
I’m working on a series of scripts, toolboxes, and notebooks within an ArcGIS Pro project. I’d like to have version control with Git, similar to what I use with VS Code. I’m not sure what the best approach is. I was thinking of initializing a .git repository directly in the folder where ArcGIS Pro stores the project, and creating a .gitignore file to exclude unnecessary files. However, I’m not sure if that’s the correct way to do it or if there’s a better alternative. Thank you.
Antonio
Solved! Go to Solution.
Hey @Antonio_Fraga
I do this exactly how you've explained, I have a ArcGIS Pro project file contained with a Git repository, this repo then is controlled using a .gitignore to prevent it from adding the aprx file, gdb, etc. Doing this allows me to see the versions of the python toolboxes, scripts, and notebooks multiple versions and allows me to publish and push to code reviewers and the like. I would say your idea is the correct move!
Cody
Hey @Antonio_Fraga
I do this exactly how you've explained, I have a ArcGIS Pro project file contained with a Git repository, this repo then is controlled using a .gitignore to prevent it from adding the aprx file, gdb, etc. Doing this allows me to see the versions of the python toolboxes, scripts, and notebooks multiple versions and allows me to publish and push to code reviewers and the like. I would say your idea is the correct move!
Cody
I pretty frequently use the commondata folder to house my repos. Or keep the toolbox in a totally separate location and set it to import by default. Here's a simple version control tool I use sometimes to keep track of branches from within Pro. And another one that lets you use Git and plaintext to manage Attribute Rules.