This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-05-17
Channels
- # babashka (34)
- # beginners (19)
- # biff (3)
- # clojure (18)
- # clojure-europe (31)
- # clojure-nl (2)
- # clojure-norway (9)
- # clojure-uk (1)
- # community-development (14)
- # datomic (11)
- # emacs (2)
- # honeysql (10)
- # hyperfiddle (20)
- # introduce-yourself (3)
- # off-topic (13)
- # pedestal (3)
- # polylith (18)
- # rdf (12)
- # releases (5)
- # uncomplicate (1)
- # yamlscript (4)
gfm() {
main=$(git symbolic-ref refs/remotes/origin/HEAD | sed 's@^refs/remotes/origin/@@')
git fetch origin $main:$main
}
gmm() {
main=$(git symbolic-ref refs/remotes/origin/HEAD | sed 's@^refs/remotes/origin/@@')
git merge $main --no-edit
}
So I can fetch from main|master
and merge to my branch, without switching branchesI've never used git aliases, but I think you're right that they are a better approach than bash functions.
However, the main=$(git symbolic-ref refs/remotes/origin/HEAD | sed 's@^refs/remotes/origin/@@')
part finds the primary branch, which is sometimes main
, sometimes master
(but rarely anything else). I wonder how I'd do that in a git alias?
Oh, I see, that’s clever. I also have update-master = "!git fetch origin master:master"
and then I have a function in Emacs figures out which is the correct one to use, and calls it
But you can do most things in a git alias, I have one like this: showt = "!show() { GIT_EXTERNAL_DIFF=difft git show ${1} --ext-diff; }; show"
, so I guess you could even just move your functions to git aliases, if you think that would be an improvement
If you use oh-my-zsh - I think you get a bunch of aliases https://kapeli.com/cheat_sheets/Oh-My-Zsh_Git.docset/Contents/Resources/Documents/index
gmom -> git merge origin/$(git_main_branch)
Morning!
Morning 🧜♀️
Morning. Other slacks I am part of have highlighted a section of Slack's https://slack.com/intl/en-gb/trust/data-management/privacy-principles#:~:text=To%20opt%20out%2C%20please%20have,opt%20out%20has%20been%20completed as a concern in relation to Slack building AI/ML models out of all comms. Namely this section: > Contact us to opt out. If you want to exclude your Customer Data from Slack global models, you can opt out. To opt out, please have your org, workspace owners or primary owner contact our Customer Experience team at <mailto:[email protected]|[email protected]> with your workspace/org URL and the subject line ‘Slack global model opt-out request’. We will process your request and respond once the opt-out has been completed. I think @seancorfield is an admin that hangs out here, is this something that the admin team is aware of?
I assume everyone would be on board with opting out, or indifferent. I vote opt out. And yeah, @seancorfield hangs here 🙂
Thank you for highlighting this issue!
I think #C0CB40N8K would be a great place to discuss this further. Not sure if Sean is in the #CBJ5CGE0G channel...
Any discussion can move https://clojurians.slack.com/archives/C0CB40N8K/p1715943124806019 - thanks
Model tuned on me and @U0525KG62 having a go at each other, I’m fairly sure AI has suffered enough 🙂
Most discussion based platforms will harvest as much data to training now to fix search problems that have caused issues over the years.
That policy has been in place since September last year but a few "outraged" threads on Twitter seem to suddenly be causing a bit of panic about it. It's been discussed in several Slacks I'm in and some folks think it's a bigger deal than other folks. Several people have reported that their employers think it's a good use of AI and are happy to have it working for them.