-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
- Github Action's design is much better, just look at [1] for example, there's a lot of low-hanging fruit in Gitlab that's not done for some reason
- I've had tons of issues with their kubernetes runners, hard to debug spurious system failures
- They still don't display the last N bytes of the logs when logs get long, just the first N bytes, which is entirely useless when a build fails
- It's awfully slow to navigate through pipelines, in particular child pipelines
- The `stages` things is just useless noise, I just wanna specify dependencies please
- You can't expose a secret to a single job step
- Github has many more reusable actions from a community, I don't think Gitlab has that at all? At least not in a convenient way.
[1] https://gitlab.com/gitlab-org/gitlab/-/issues/395964
I made a garbage tool to pull repositories from gitlab to github or vice versa. I used it just to explore Go so it's not really prod ready but handy if you're just looking to move your code over.
It most likely will explode.
https://github.com/tylerjgarland/git2git
It looks like gitea supports running a proc_receive hook which can be used to implement pull requests over git:// using a client like https://git-repo.info/en/
(full disclosure) I had written a proof of concept implementation that allows you to use the git-repo.info client to send PRs over git protocol, which you can find here https://github.com/pullreqr/pullreqr_githook
The primary impediment seems partially to be social/coordination where distributed git requires clients to be set up apriori, but it does work in cases where you are using it in house, etc.
I'd kind of be happy to spend more time on it, but with no one actually running the protocol publicly, there is no one to send/receive PRs to or from.
