I also blogged about my motivations for writing Release Train here: https://willabides.com/posts/release-train-continuous-releas...
HN user
WillAbides
[ my public key: https://keybase.io/wroden; my proof: https://keybase.io/wroden/sigs/3j64M5xg4rAu52zI8RkvjuckwdmTFMkusVOfaWq9fQA ]
hnchat:eWY4KMH4MUJK6UDQDnq7
Release Train will automatically create a new GitHub release every time you merge a pull request into main or whatever release branches you set up. It's inspired by semantic-release[1] but takes a different approach. Instead of using commit messages it uses PR labels to determine the type of release. This makes it easier to use. It's also a single binary so it doesn't require npm or any other package manager.
It comes in the forms of both cli and GitHub Action.
The downside of this approach is that it ties you to GitHub. It could be extended or forked to support any platform that has something like a pull request with labels. I'm comfortable adding that to the technical debt I will incur migrating away from GitHub.
I would love to get notes from the hn community on this.
You’ve got me beat. https://willabides.com. I haven’t posted anything yet.
related blog post: https://github.blog/2021-06-23-introducing-new-github-issues...
For anybody who stumbles across this and is interested, this conversation is continued on reddit.
https://old.reddit.com/r/golang/comments/mlhvx0/i_wrote_yet_...
I apparently had a fundamental misunderstanding of the meaning of branchless. That's embarrassing.
As for simdjson-go, I did benchmark it. rjson outperformed simdjson-go in most benchmarks, but simdjson-go was about 3% faster reading citm_catalog.json.
https://github.com/WillAbides/rjson#simdjson
Edit:
I see on your bio that you are one of the simdjson authors. I hope you will indulge a question about it. I am generally more interested parsing a large volume of json documents efficiently than I am in doing it quickly. Since simdjson uses parallel instructions, would that mean that the speedup comes at the expense of being able to process more documents in parallel on the same hardware?
I wrote a mostly branchless json parser in go using ragel to generate most of the code.
https://github.com/WillAbides/rjson
The generated code isn't much to look at, but it is certainly fast.
https://github.com/WillAbides/rjson/blob/main/object_handler...
I’m not involved in this project, but I would guess that it’s because it validates both issues and PRs, but only PRs have statuses on GitHub, More precisely, only commits have statuses, and issues aren’t associated with commits.
“avatar_url” is the only part of that endpoint in preview, so that warning only applies to that field. I can see how the notification isn’t clear on that point, and I will bring that up.
I don't think they store all their data on twitter. If they did, they probably wouldn't have this file in their repo: https://github.com/edent/openbenches/blob/master/database/da...
I didn’t spend hundreds of dollars on a mechanical keyboard with custom caps and switches to “click”.
This brings back a memory of a conversation with my grandfather. We were in Midland, and I said something about heading over to Odessa. He made a disparaging remark about my intelligence and said we would have to head out to Odessa from there.
That never made any sense to me until now.
Git Flow and GitHub Flow are actually distinct from each other. Here's a blog post about it from Scott Chacon.
"really really fixed this time for real"
I didn't notice that was Mitchell. Makes sense. The one time I met him in person we talked about Tesla.
Now I need to track down Elon Musk to discuss Consul.
Taste is dependent on the audience. An audience of kernel maintainers would probably share Linus' taste here, while an audience of enterprise developers would find the original code more palatable.
ipnon was probably talking about the cal command in the body of the message.
What do feelings have to do with science?
When the science in question is psychology, feelings have everything to do with it.
What do you think `git branch` should do?
Don't participate
Chip implants
That makes sense. I use RubyMine's refactoring to rename all instances of a variable, but if that weren't available multi-cursor would certainly be a lot easier than copy-pasting.
You can open random files with it. From the command line, type `idea <filepath>`. If you already have a project open, the file will open in the same window as that project, but it isn't tracked as part of the project. If you don't have IntelliJ open yet, it starts a new instance with just that file.
That being said, even though I'm more comfortable with Jetbrains' editors, I still tend to edit miscellaneous docs in atom or vim.
What do you actually use multi-cursor for in typical coding? I tried it out when it was introduced in IntelliJ. I thought it was cool, but I've not run into any uses for it in the years since.
There is no shortage of people and companies trying. The trouble is that none of them have the operational experience to make it work.
The cc addresses work great with Google Inbox bundles. Thanks for adding that.
93% male / 4% female / 3% undisclosed.
source: https://medium.com/@tenaciouscb/github-com-demographics-a-st...
I'm looking at this one [0]. Specifically this item in the FAQ:
Will GitHub force me to move to per-user pricing after 12 months?
No. At this time we are not enforcing a timeline to move and if in the future we do decide to set a timeline we are committing to giving you at least 12 months.
[0] https://github.com/blog/2164-introducing-unlimited-private-r...
This has almost quadrupled our monthly cost ($850 vs $2914)
Has it really? Existing orgs aren't being forced to change, and on top of that they say they will give at least 12 months notice if they decide to force existing orgs into new pricing.
Check the bottom of this page [0] and prepare to be thrilled.