Content
github picks the wrong branch to display file contents
Added by Sarah Sharp almost 8 years ago
Greetings! I’m a coordinator for Outreachy, a non-profit program dedicated to providing internships to people traditionally underrepresented in tech. We’ve been looking around for an open source tool to help us keep track of Outreachy project goals, and one of our top priorities is that the tool be open source.
I was happy to see OpenProject’s code available on github. However, I ran into a series of issues that initially made me feel like project isn’t as welcoming to newcomers. Most of these issues stem from github picking the “dev” branch as the branch to display file contents from in the web interface. If you can find a way to indicate to github what the main branch should be, you’ll avoid most of these negative first impressions:
- The link to OpenProject’s CLA in leads to a 404: https://www.openproject.org/wp-content/uploads/2014/09/OPF-Contributor-License-Agreement_v.2.pdf (providing a redirect would be good)
- The github issues are disabled, and there is no indication of where to file bugs in the CONTRIBUTORS.md (again, because this was on the “dev” branch, the stable-6.1 branch does have this information)
- The CONTRIBUTOR.md on the “dev” branch mentioned the gitter channel. When I clicked on it, the last message was in September of last year, saying gitter was no longer used, and linked to the community forums here. (providing a note on that channel about the community forums that are now used would be good)
Until I started filing this bug report, I didn’t realize the github page was on the “dev” branch. I suspect many contributors are going to have the same issue, which is why I’m leaving this detailed report in hopes that you can find a work-around on github. I will also leave this bug report in the official bug tracker (now that I’ve found it).
Replies (3)
It looks like it’s a pretty simple fix for the OpenProject github admin: https://help.github.com/articles/setting-the-default-branch/
Hi Sarah,
thanks a lot for your post - good points.
The dev-branch is the one you should work on. We updated the contributions.md last week in the 6.1 branch. We manually merge changes from the release branch to the dev branch. I guess we should do this more regularly.
https://github.com/opf/openproject/blob/dev/CONTRIBUTING.md
Are you interested in working on OpenProject?
Best
Niels
I’m most likely to contribute if I find a bug or want some feature (like being able to duplicate a project but shift all the deadlines by six months — each Outreachy round starts with the same tasks).