Working with Github

Asked

Viewed 208 times

2

We are with a project to create an application server based on J2EE + Glassfish in order to update the way we work in our company.

In this environment, two programmers will work on the same project, and we chose Git as a versioning tool.

My question is: To use Git, do I create an account for each programmer + an account for the server? Do I use an account only as a project repository? I am layman to use versioning system, I have read enough but it has not entered the right idea in my head.

git github versioning

  • I think a good way to go would be to search the questions already made here on the site, has enough content that can clarify better the functioning

  • 1

    Is this about github or Git? Is it going to be github or are you going to create local repositories with a local master? Or are you using private Github?

  • A guide for anyone who wants to start using Git (independent of github, bitbucket, gitlad, etc), is divided into topics: git-for-Beginners-the-definitive-Practical-guide, Not much use for a tool without knowing how to use it, right? If you implement in your company and have no idea how to use it I think you will have more problems than solutions.

  • Thank you to everyone who has helped me. I am scouring when I have plenty of time on the job, trying to soak up as much coinhecimento.

  • @Guilhermenascimento We would use a private Github. At first we will be free to work on this issue here within the company, being able to test and reevaluate freely. I’m not crazy to implement something I have no knowledge of on a hehehe production basis. But thank you so much for the feedback and the willingness to respond.

  • That’s why I indicated the link/material with the topics to start in "Git", there are many people I know on the site who complain for example that you can’t commit directly in master and how to get around this, but getting around this is the same as "kill" The basic Git and Versioning control foundation, which controls Master, is always one (or more people), and other employees make copies and send them as a pull-request for the "Masters" to evaluate. To do the truth I’m sure there are companies that allow anyone to commit to "master".

Show 1 more comment

2 answers

5


Ideally, you have an account for the company, not the server. If the company has other projects later on, you can create one repository per project.

With a single account for the company you can then use cool things like Jenkins or Hudson, which are tools that help automate various tasks and integrate with version control systems.

As versioning is difficult to understand, in my experience people only really understand after using and feeling in practice the advantages that it brings.

  • 1

    I agree 1000% with that statement: As versioning is difficult to understand, in my experience people only really understand after using and feeling in practice the advantages that it brings.

  • 1

    Got it. That question of practice I fully agree too, thank you for the reply.

0

To use GIT, it doesn’t necessarily have to be with Github, there are other platforms that make GIT available as Version control, such as Bitbucket, Gitlab, Visual Studio Team Services.

Just like Renan said in another answer, you can use a number of other tools, as he himself quoted, Jenkins, Hudson, etc..

I know a lot about Visual Studio Team Services, so my suggestion to you is to use this tool, for the following points:

  1. It’s Online, Free for 5 Developers and Unlimited Stackholders
  2. You can create free unlimited repositories for your sources, whether using TFVC or GIT;
  3. You can manage your backlogs and integrate with your changes to the source code;
  4. You can also have automated build processes, with testing validations, architectures, quality, etc;
  5. You can have Automated Deployment processes as well.
  6. You can create a Wiki for your project

These functions above, you can use for free on VSTS in the case with up to 5 developers. You can also, by paying the part, have your server nuget and npm private.

The Cool, is that all this works not only for Microsoft technologies, you can manage for example your Java project, automate builds, and Deployment of Java applications, including using linux servers to build and/or Deployment destination.

About learning git, there is a lot of good stuff on the internet, for example:

If you want to know more about VSTS, I have a playlist on my channel on the subject

Browser other questions tagged git github versioning

You are not signed in. Login or sign up in order to post.