Native Go
@v-priyagupta108 is already working on this.
Since Sep 11, 2026.
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 673
- Avg merge
- 6d 28m
- Merged PRs (30d)
- 4
Description
Description:
I saw today Node 20 deprecation notice in our CI piplines.
To my surprise major Go CI action is using Typescript?
This is so strange. Why Go ecosystem that is notoriouslty does not even depend on libc to do syscalls now is depending on a dependency/security nightmare JS/Typescript ecosystem?
More to that. Since recently, Typescript itself uses Go. So to build a Go project we depend on something that is itself depends on Go itself to be built! Why we have this extra jump into Typescript land?
Go has notoriously high stability and security of its packages. Minimialism in dependencies.
Typescript/Node is notoriously nightmare. Fiasco after Fisasco. Every year something happens.
Why we are not utilising Go to build CI ecosystem for Go projects?
What are we even doing here.
Justification:
like cmon.
Are you willing to submit a PR?
Yes.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.