3 ms·

> Hackers, working alone, late at night, strange times, strange places. Cultivating their work and skills and then ... shoot ... sending an email! Very poetic,

by dewey 3y ago

> Hackers, working alone, late at night, strange times, strange places. Cultivating their work and skills and then ... shoot ... sending an email! Very poetic, but also not much different to the current state. Just clicking to open a PR instead of sending an email attachment.

nkjoep 3y ago
correct. Opening a PR triggers an email. No difference at all.
keepamovin 3y ago
:) Thank you! I guess I prefer text. And deeply there's a difference between staying in text, and moving to GUI. The medium is the message^0, and even if the process is "the same", everything becomes different because you're no longer within the text world. 0: https://en.wikipedia.org/wiki/The_medium_is_the_message https://en.wikipedia.org/wiki/The_medium_is_the_message
- dewey 3y ago
  I know it's not the same, but that's also why I prefer GitLab's "--push-option=merge_request.create" which creates a PR from the CLI without needing me to open the website and clicking a button. I'm still annoyed daily that this doesn't exist for GitHub.
  - pjm331 3y ago
    GitHub has a CLI https://cli.github.com/manual/gh_pr_create https://cli.github.com/manual/gh_pr_create
    - dewey 3y ago
      Yes, but the advantage with the "push options" is that I can put it in my .gitconfig and it just works automatically when I do a git push without using some proprietary platform's cli.
  - dnsmichi 3y ago
    Thanks for sharing. GitLab team member here. More GitLab push options are documented in https://docs.gitlab.com/ee/user/project/push_options.html https://docs.gitlab.com/ee/user/project/push_options.html You can also add a parameter to merge the merge request when the pipeline succeeds. This can be handy for quick fixes that do not require reviews, and avoids unnecessary context switches. # mwps BRANCHNAME alias mwps='git push -u origin -o merge_request.create -o merge_request.target=main -o merge_request.merge_when_pipeline_succeeds' Example from https://gitlab.com/sytses/dotfiles/-/blob/master/git/aliases.zsh?ref_type=heads#L24 https://gitlab.com/sytses/dotfiles/-/blob/master/git/aliases... and https://about.gitlab.com/blog/2021/10/19/top-10-gitlab-hacks/#create-with-confidence https://about.gitlab.com/blog/2021/10/19/top-10-gitlab-hacks... If you prefer deeper CLI integration, suggest installing the GitLab CLI: https://docs.gitlab.com/ee/editor_extensions/gitlab_cli/ https://docs.gitlab.com/ee/editor_extensions/gitlab_cli/

by dewey 3y ago

nkjoep 3y ago

correct. Opening a PR triggers an email. No difference at all.

keepamovin 3y ago

:) Thank you! I guess I prefer text. And deeply there's a difference between staying in text, and moving to GUI. The medium is the message^0, and even if the process is "the same", everything becomes different because you're no longer within the text world. 0: https://en.wikipedia.org/wiki/The_medium_is_the_message https://en.wikipedia.org/wiki/The_medium_is_the_message

dewey 3y ago
I know it's not the same, but that's also why I prefer GitLab's "--push-option=merge_request.create" which creates a PR from the CLI without needing me to open the website and clicking a button. I'm still annoyed daily that this doesn't exist for GitHub.
- pjm331 3y ago
  GitHub has a CLI https://cli.github.com/manual/gh_pr_create https://cli.github.com/manual/gh_pr_create
  - dewey 3y ago
    Yes, but the advantage with the "push options" is that I can put it in my .gitconfig and it just works automatically when I do a git push without using some proprietary platform's cli.
- dnsmichi 3y ago
  Thanks for sharing. GitLab team member here. More GitLab push options are documented in https://docs.gitlab.com/ee/user/project/push_options.html https://docs.gitlab.com/ee/user/project/push_options.html You can also add a parameter to merge the merge request when the pipeline succeeds. This can be handy for quick fixes that do not require reviews, and avoids unnecessary context switches. # mwps BRANCHNAME alias mwps='git push -u origin -o merge_request.create -o merge_request.target=main -o merge_request.merge_when_pipeline_succeeds' Example from https://gitlab.com/sytses/dotfiles/-/blob/master/git/aliases.zsh?ref_type=heads#L24 https://gitlab.com/sytses/dotfiles/-/blob/master/git/aliases... and https://about.gitlab.com/blog/2021/10/19/top-10-gitlab-hacks/#create-with-confidence https://about.gitlab.com/blog/2021/10/19/top-10-gitlab-hacks... If you prefer deeper CLI integration, suggest installing the GitLab CLI: https://docs.gitlab.com/ee/editor_extensions/gitlab_cli/ https://docs.gitlab.com/ee/editor_extensions/gitlab_cli/