I have some dumb #Drupal FOSS contributing questions. I keep noticing that people are opening merge requests against the 8.x-1.x-dev branch in GitLab when the current release is 8.x-4.x.
That's an error right? Is this just a quirk of making it so easy to contribute code?
It seems like it has to be an error to me, but I've seen it so many times. Also when I've opened a merge request, GitLab seems to be steering me in the direction of issuing the MR against the 1.x-dev branch.
For example, I'd create an issue fork off the 4.x-dev branch and when I open a merge request, it's defaulting me to the 1.x-dev branch. Is that intentional or just a quirk to watch out for?
Also, what's the proper etiquette for when there's no -dev branch to issue a MR against? Should I just make the MR against the main branch?
@sysop408 in that case the maintainer needs to set the default branch in the project settings. It's worth opening a task issue in their queue asking them to do that so it doesn't impact the next unsuspecting contributor too.
What project are you trying to contribute to? Drupal core's default branch is now 11.x. But there are different modules/themes that have different branches.
but yeah, I echo what Tim said, get into #contribute in Drupal Slack and you can ask questions there :)
Or feel free to reply here, and I'll get to it when I see it
Add comment