52
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 01 Sep 2023
52 points (89.4% liked)
Technology
58157 readers
3586 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
Unfortunately I don't think your experience is unique. I've seen several open source projects suffer from cliquey, protectionist behavior. I've been on a project where I was told by the primary developer to rebase my PR branch onto origin/main or it won't get looked at. By the time I've done that, that same developer's already pushed a commit directly to origin/main, and I'm no longer up-to-date.
Your case is pretty common with any project IME and it's not "cliquey" behavior. People really dont want to waste their time on something that's not ready to merge, and if the branch is pretty out of date it's probably not ready. I really doubt they'd complain about it being off by a commit or two, unless a merge conflict has come up since maybe.
Nah, we're talking a timescale of minutes here, a few hours at best. New feature, no conflicts, ready to merge. Fetch, rebase, push. Out of date almost immediately. Fetch new commit, rebase, push. Minutes later, out of date again.
See what I learned is, you can't outpace the sole project owner and principal developer, no matter how many other contributors the project has. Especially if he gets paid to work on the project full time. How do you compete with someone who has direct push access, commits every half hour, doesn't check PR's, and mandates rebases for fast-forward-only merges?
So my takeaway was, you don't. They're just not that into the feature, why should I be? Leave the branch exactly the way it is until someone asks for it to be made ready. They get 3 chances. If they don't merge it after asking for it 3 times, I tell them to checkout the branch themselves and take over. If I get code review feedback 3 times, I ask for peer programming. If they can't schedule it or don't want to, tell em check out the branch themselves and take over.
If they've got better things to do with their time, then you bet your sweet bippy I got better things to do with mine.