home.social

#shitlab — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #shitlab, aggregated by home.social.

  1. When you click on "Merge train" in a #gitlab PR that has a different target branch than the default branch, you are forwarded to a page that lists merge trains...

    FOR THE DEFAULT BRANCH INSTEAD OF THE TARGET!!!

    What do they do for a living over at gitlab?

    #shitlab

  2. When you click on "Merge train" in a #gitlab PR that has a different target branch than the default branch, you are forwarded to a page that lists merge trains...

    FOR THE DEFAULT BRANCH INSTEAD OF THE TARGET!!!

    What do they do for a living over at gitlab?

    #shitlab

  3. When you click on "Merge train" in a #gitlab PR that has a different target branch than the default branch, you are forwarded to a page that lists merge trains...

    FOR THE DEFAULT BRANCH INSTEAD OF THE TARGET!!!

    What do they do for a living over at gitlab?

    #shitlab

  4. When you click on "Merge train" in a #gitlab PR that has a different target branch than the default branch, you are forwarded to a page that lists merge trains...

    FOR THE DEFAULT BRANCH INSTEAD OF THE TARGET!!!

    What do they do for a living over at gitlab?

    #shitlab

  5. When you click on "Merge train" in a #gitlab PR that has a different target branch than the default branch, you are forwarded to a page that lists merge trains...

    FOR THE DEFAULT BRANCH INSTEAD OF THE TARGET!!!

    What do they do for a living over at gitlab?

    #shitlab

  6. *times out your SSO*
    *times out your SSO*
    *times out your SSO*
    *times out yo

    #GitLab #ShitLab

  7. *times out your SSO*
    *times out your SSO*
    *times out your SSO*
    *times out yo

    #GitLab #ShitLab

  8. *times out your SSO*
    *times out your SSO*
    *times out your SSO*
    *times out yo

    #GitLab #ShitLab

  9. *times out your SSO*
    *times out your SSO*
    *times out your SSO*
    *times out yo

    #GitLab #ShitLab

  10. *times out your SSO*
    *times out your SSO*
    *times out your SSO*
    *times out yo

    #GitLab #ShitLab

  11. #shitlab comment window does not work with keybindings

    🙄 🤦

  12. #shitlab comment window does not work with keybindings

    🙄 🤦

  13. #shitlab comment window does not work with keybindings

    🙄 🤦

  14. #shitlab comment window does not work with keybindings

    🙄 🤦

  15. #shitlab comment window does not work with keybindings

    🙄 🤦

  16. Who in their FUCKING right mind decided that when I reply to a comment in #shitlab #gitlab that it would be a good idea to "Start a new Review"???

    WHAT SHITHEAD DECIDED THAT THIS WAS A GOOD IDEA?

  17. Who in their FUCKING right mind decided that when I reply to a comment in #shitlab #gitlab that it would be a good idea to "Start a new Review"???

    WHAT SHITHEAD DECIDED THAT THIS WAS A GOOD IDEA?

  18. Who in their FUCKING right mind decided that when I reply to a comment in #shitlab #gitlab that it would be a good idea to "Start a new Review"???

    WHAT SHITHEAD DECIDED THAT THIS WAS A GOOD IDEA?

  19. Who in their FUCKING right mind decided that when I reply to a comment in #shitlab #gitlab that it would be a good idea to "Start a new Review"???

    WHAT SHITHEAD DECIDED THAT THIS WAS A GOOD IDEA?

  20. Who in their FUCKING right mind decided that when I reply to a comment in #shitlab #gitlab that it would be a good idea to "Start a new Review"???

    WHAT SHITHEAD DECIDED THAT THIS WAS A GOOD IDEA?

  21. Re-reading #email patch workflow stuff and the #b4 and #publicinbox docs and ... maaan... that is the only true way of developing software together in large teams.

    I mean, I don't care for your 5 person project, do what you want.

    But for large projects, that really is the only way to develop that truly scales.

    Maybe, just maybe, #radicle can become the second way of doing that. Right now, it clearly is not (mainly because it is too young), but I still have hope!

    That said, #sourcehut is also really nice, but right now I like public-inbox a bit more. I guess you could combine the two, possibly?

    #git #github #shithub #gitlab #shitlab

  22. Re-reading #email patch workflow stuff and the #b4 and #publicinbox docs and ... maaan... that is the only true way of developing software together in large teams.

    I mean, I don't care for your 5 person project, do what you want.

    But for large projects, that really is the only way to develop that truly scales.

    Maybe, just maybe, #radicle can become the second way of doing that. Right now, it clearly is not (mainly because it is too young), but I still have hope!

    That said, #sourcehut is also really nice, but right now I like public-inbox a bit more. I guess you could combine the two, possibly?

    #git #github #shithub #gitlab #shitlab

  23. Re-reading #email patch workflow stuff and the #b4 and #publicinbox docs and ... maaan... that is the only true way of developing software together in large teams.

    I mean, I don't care for your 5 person project, do what you want.

    But for large projects, that really is the only way to develop that truly scales.

    Maybe, just maybe, #radicle can become the second way of doing that. Right now, it clearly is not (mainly because it is too young), but I still have hope!

    That said, #sourcehut is also really nice, but right now I like public-inbox a bit more. I guess you could combine the two, possibly?

    #git #github #shithub #gitlab #shitlab

  24. Re-reading #email patch workflow stuff and the #b4 and #publicinbox docs and ... maaan... that is the only true way of developing software together in large teams.

    I mean, I don't care for your 5 person project, do what you want.

    But for large projects, that really is the only way to develop that truly scales.

    Maybe, just maybe, #radicle can become the second way of doing that. Right now, it clearly is not (mainly because it is too young), but I still have hope!

    That said, #sourcehut is also really nice, but right now I like public-inbox a bit more. I guess you could combine the two, possibly?

    #git #github #shithub #gitlab #shitlab

  25. Re-reading #email patch workflow stuff and the #b4 and #publicinbox docs and ... maaan... that is the only true way of developing software together in large teams.

    I mean, I don't care for your 5 person project, do what you want.

    But for large projects, that really is the only way to develop that truly scales.

    Maybe, just maybe, #radicle can become the second way of doing that. Right now, it clearly is not (mainly because it is too young), but I still have hope!

    That said, #sourcehut is also really nice, but right now I like public-inbox a bit more. I guess you could combine the two, possibly?

    #git #github #shithub #gitlab #shitlab

  26. @totoroot es stört mich das praktisch nichts funkioniert bei dem Scheissteil.

    Der Toot war tatsächlich weil #shitlab zu Blöd ist ein PR-Review als dismissed zu markieren wenn neu gepushed wird, und weil man nicht reviewen kann wenn man nicht requested wurde.

    Und nur weil andere Tools noch beschissener sind heisst das ja auch nicht das #gitlab gut ist.

  27. @totoroot es stört mich das praktisch nichts funkioniert bei dem Scheissteil.

    Der Toot war tatsächlich weil #shitlab zu Blöd ist ein PR-Review als dismissed zu markieren wenn neu gepushed wird, und weil man nicht reviewen kann wenn man nicht requested wurde.

    Und nur weil andere Tools noch beschissener sind heisst das ja auch nicht das #gitlab gut ist.

  28. @totoroot es stört mich das praktisch nichts funkioniert bei dem Scheissteil.

    Der Toot war tatsächlich weil #shitlab zu Blöd ist ein PR-Review als dismissed zu markieren wenn neu gepushed wird, und weil man nicht reviewen kann wenn man nicht requested wurde.

    Und nur weil andere Tools noch beschissener sind heisst das ja auch nicht das #gitlab gut ist.

  29. @totoroot es stört mich das praktisch nichts funkioniert bei dem Scheissteil.

    Der Toot war tatsächlich weil #shitlab zu Blöd ist ein PR-Review als dismissed zu markieren wenn neu gepushed wird, und weil man nicht reviewen kann wenn man nicht requested wurde.

    Und nur weil andere Tools noch beschissener sind heisst das ja auch nicht das #gitlab gut ist.

  30. @totoroot es stört mich das praktisch nichts funkioniert bei dem Scheissteil.

    Der Toot war tatsächlich weil #shitlab zu Blöd ist ein PR-Review als dismissed zu markieren wenn neu gepushed wird, und weil man nicht reviewen kann wenn man nicht requested wurde.

    Und nur weil andere Tools noch beschissener sind heisst das ja auch nicht das #gitlab gut ist.