These are just JSON files... There is hardly any code/logic at all from these files. As an engineer, this is far from a big github commit. If anything, it's a set of initial commits to a repo.
UPDATE: if you go to the commit tracker here, you can see that there has only been 3 commits to this repo.
Webdeveloper here. When someone in my company starts to work on a project, we set up deployment for local testing, integration, staging and production in the beginning. We do it because we want everything to go smoothly when we finally want to deploy our project.
Setting up everything when you already have a lot of code can get a lot messier, since if something goes wrong, you have a lot more sources of potential errors you have to go through. If you set it up in the beginning, you know that the deployment circle is working and if something goes wrong, the error is somewhere else.
In the end it's up to the developers what kind of workflow they prefer. I just know that's its not unusual to configure a lot from the beginning, even though you don't already need it.
Just look at the comments. "first real commit", "initial commit". Nothing big in there. Just basic setup of a new repo, so multiple people can start working on it.
22
u/GunplaAddict Jan 25 '18 edited Jan 25 '18
These are just JSON files... There is hardly any code/logic at all from these files. As an engineer, this is far from a big github commit. If anything, it's a set of initial commits to a repo.
UPDATE: if you go to the commit tracker here, you can see that there has only been 3 commits to this repo.