Collaborating on GitHub is a real challenge

There are so many things and so many subtle different ways you can do things on Git and GitHub. It’s one thing to learn how to use it for yourself but an entirely different story to collaborate with others on the platform. Every little nuance of and detail of what you do communicates something to the team. You can end up irritating other people without even knowing. And people do get pissed.


But what else can we do except stumble first before achieving proficiency?

Codecademy, when you make your giithub path, please explain exactly what every single action you do signals to the team, the broader context of what the different actions and commands on Git communicate. And how to communicate properly on GitHub as well like for example how to copy permalinks of lines, etc.

Yep, communication—clear communication–is key to collaboration. If one hasn’t worked in a collaborative environment (either at work or school), then it’s a challenge. Even when one has been doing it for years, you’ll be working with many different people with different knowledge bases and backgrounds, strengths & weaknesses, etc. Even when you may think you’re being clear, always be open to constructive criticism.

1 Like

To be clear, I am more specifically emphasizing collaborating using GitHub as a challenge compared to broad, general collaboration soft skills.

Yep! I know what you meant.
Still applies. :slight_smile:

Honestly, it sounds like you’re collaborating with someone who has an attitude. In my experience, most open source collaboration is not like this. Occasionally you’ll find someone with an ego or an attitude who ruins it for everyone, but that’s not the norm – at least not if you get involved with a decent sized organization or project.

I’m sorry that this has been your experience so far, but hopefully that doesn’t discourage you from future collaboration. And remember, if you ever have any questions about Git or GitHub, you can always ask them here or on the Discord server. There are a decent number of people on both who should be able to help you out if there’s something you’re unsure about.

I think I’m misunderstanding the complaint here. The discord user is annoyed that you are asking for a code review in the first comment? That comment is a valid complaint, as someone who has done code reviews for PRs. Doing a code review can be a very intensive and complicated job, depending on the level of changes being proposed, and the vast majority of GitHub users are volunteers. I sense more of a passive annoyance than any negativity in that comment, and it isn’t directed at you in particular but at the more general annoyance of doing a review.

The second comment doesn’t seem like a complaint directed at anybody in particular to me, more of a complaint about faults in the GitHub UX.

But in general, I would encourage you to consider their perspective. As a project maintainer, I have had to reject proposals, PRs, and give negative feedback to people who weren’t very helpful to the project. I don’t have a personal problem with anybody, and I try to always be encouraging by reminding them that it’s not their skill as a developer I am rejecting, but their specific request. Communicating with strangers is hard, especially with people on the other side of the planet. The person you are responding to is probably looking at several different things that need to be done with the project, sees your code review request, and views it as just another task on a growing pile of work. I guarantee you 100% its nothing personal, nor is it directed at you specifically.

If you have any specific concerns about collaborating on GitHub, like I said, I am a project maintainer, so I can answer questions you have that might be lacking in the Codecademy materials.