Earlier quoted context omitted.
As much as I’ve been frustrated by these outrages, we’ve all been there
Now that is a good typo
could be on purpose
Incident with Issues and Pull Requests
91–100 of 143 posts
Re: Incident with Issues and Pull Requests
#92Earlier quoted context omitted.
Gitea's ability to create a local repository as mirror of a remote repository is great for this. You can stay on Github and have your code regularly mirrored locally.
If only Git had this sort of functionality built in…
Gitea can run your CI actions too, and host your releases.
Re: Incident with Issues and Pull Requests
#93Back to biz
Re: Incident with Issues and Pull Requests
#94Just lost a merge commit to dev/null. This is getting tiresome
How??? You do the merge, which either creates a new commit for the change, or appends the commits to your existing tree. Then you push that to the remote. If the push fails, you can just push again, it's not lost. And if the merge failed, you didn't have any merge commit to begin with.
May have been using the GitHub interface
Re: Incident with Issues and Pull Requests
#95I'm going to self-host my git repos. Any recommendations? The git+nginx would suffice but it does not offer GUI. I need one to see the changes proposed (aka PRs). Gitea is nice, but a bit overkill for my needs. I don't need CI, files hosting, issues, team members, releases, wiki, forking/watching/staring, etc.
imho Gitea is so smooth to deploy and manage that it's worthwhile even if you don't need its advanced features.
Re: Incident with Issues and Pull Requests
#96Earlier quoted context omitted.
Yeah, Gitlab has had its share of downtime. Github has had shockingly little until the last year or two. These things come and go. Of course, if this continues happening it may be time for the OSS community seriously consider migrating en masse. [Edit to fix grammar - thanks for the corrections!]
FWIW the typical phrase is "en masse" (which is French). The English translation is "in mass".
The English translation would be something like, “all together, at the same time”. “In mass” isn’t an English idiom.
Re: Incident with Issues and Pull Requests
#97Does anyone host their own git repos in an enterprise environment? How do you do it and what are some good resources for learning how to do this?
Yes, we do this using https://gitea.io/en-us/ on a private server (firewall, backups and a replica) for most projects. Github is only used when it's required by a stakeholder.
Gitea here. Should disclose that we ended up contributing to the project and developing an understanding of its code in order to integrate into our org, so ymmv. (but at least you can see the source).
Re: Incident with Issues and Pull Requests
#98Earlier quoted context omitted.
FWIW the typical phrase is "en masse" (which is French). The English translation is "in mass".
The English translation would be something like, “all together, at the same time”. “In mass” isn’t an English idiom.
"en masse" is the term used in English as well.
Re: Incident with Issues and Pull Requests
#99Is it time to move back to Jenkins? :X
Now that gitea supports act_runner (and hence a reasonably usable clone of GH actions), Jenkins is dead.
Re: Incident with Issues and Pull Requests
#100I'm considering host a gitea instance backup all of my repos. I have an important fix that need to be deployed right now but there is no way to deploy it in a normal way with our CI which one was setup with Github Action. Fortunately I have a instruction to bypass CI and build the source by myself. But again, Github defeat me because our release workflows are depend on GitOps which are effected by Github issue. Ahhhh…
Gitea's ability to create a local repository as mirror of a remote repository is great for this. You can stay on Github and have your code regularly mirrored locally.
Or use Gitlab. I remember doing a mirror syncing from Github with one of my gitlab repository. The main reason I used to do it is Gitlab offer free built-in CI at that time
In my case one of most important thing is the GitOps workflow. It's single source of truth so it's also single point of failure ;(