#MergeRequests

Kevin Karhan :verified:kkarhan@infosec.space
2024-10-22

@mike I think a lot of #metrics re #software and espechally #FLOSS are bs.

2024-05-01

Something I tell juniors, but I think a few experienced devs could also benefit from: Review your own PRs

thisgetthoughts.bearblog.dev/d

#juniordevs #dev #MergeRequests

2023-08-17

Our team is still using the 2018 Gitlab's recommended method solve CHANGELOG conflict nighmare.

๐Ÿค”Just curious if there's a more 2023 approach?

Help us: share your thoughts!

#git #github #Gitlab #MergeRequests #CHANGELOG #efficiency

about.gitlab.com/blog/2018/07/

JoeY โ˜•๏ธ๐ŸŽฎโœ๏ธ๐Ÿฝjoeyjr@mastodon.online
2023-02-20

Reminder to self. Don't write comments on tests and/or code. Lest merge requests get blocked because there's unwanted code (read: it's a comment, not code!) in the commit. ๐Ÿ˜†
#CodeReviews #MergeRequests #lifeofadeveloper #rants

2022-11-19

@aral @thom

Just to clarify @ new arrivals: Musk has not given his $US 44G to the Fediverse, and we don't have a centralised kitty to pay the developers who left the birdsite and "employ" them.

Find ways to support the developers of #Pleroma, #Pixelfed and so on: provide money or comment usefully on #GitRepository issues (or at least upvote their priority) or propose #MergeRequests with the required features or provide detailed bug reports.

Software is developed by people.

Client Info

Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst