3 ms·

I love that GitLab allows you to just push your repository directly: https://docs.gitlab.com/ee/user/project/working_with_projects.html#create-a-new-project-wi

I love that GitLab allows you to just push your repository directly: https://docs.gitlab.com/ee/user/project/working_with_projects.html#create-a-new-project-with-git-push https://docs.gitlab.com/ee/user/project/working_with_project... Unfortunately, I keep forgetting about that and keep creating the project by hand (also gives me some time to pause and think about naming / description, and set repo visibility for a public project). UPD: Gitea / Forgejo takes it one step further and allows you to specify visibility when pushing like this: git push -o repo.private=false -u git@git.example.com:example/hello master (Doesn't seem to work on Codeberg, though) https://docs.gitea.io/en-us/push-options/ https://docs.gitea.io/en-us/push-options/

codetrotter 4y ago
This page is not readable on my iPhone :( Here is a more readable version of that same page: https://archive.is/nRpOi#create-a-new-project-with-git-push https://archive.is/nRpOi#create-a-new-project-with-git-push
- notpushkin 4y ago
  Huh, that's weird – I've just checked and it looks fine on my Android, and in Safari in responsive design mode. :thinking:
smaudet 4y ago
I think this tool has merit where gh doesn't, in that it can/could integrate with other hosts. Github is a cancer on the git community - I know we tend to like "easy, fast, convenient" so mega-providers like GH or Gitlab are bound to occur, but we invariably find the downsides (centralized censorship, product placement, loss of features or random security vulns due to companies forgetting that the "simple" system is actually built on something complex) in the longterm. I'm not saying GH shouldn't exist, what would be even cooler is if a tool like wfh, in addition to pushing folders to github/gitlab, could push folders to arbitrary servers - if you own the domain/server and have the appropriate access, brand new git repo auto-hosted.
- chiefalchemist 4y ago
  Agreed. These platforms want you locked in. Having agnostic tools helps you sleep at night, and keep them more honest than they might be otherwise.
- notpushkin 4y ago
  It's not that bad actually, self-hosting is a thing – if you own the server, just set up your own Gitea or GitLab CE or something. I still prefer big instances myself though: most of my code is on GitLab.com, and some on Codeberg :-) Shameless plug: I'm working on a tool which lets you get Gitea (or anything else that can be run with a docker-compose) running on a server in a couple minutes. You can install it with a single curl | sh, then you get a nice panel in which you can paste your Compose file, make a couple tweaks and click Deploy. Gitea is actually the example app I picked for tutorial: https://lunni.dev/deploy/ https://lunni.dev/deploy/
- vorpalhex 4y ago
  There was an effort (though it seems to have died out) to bring federation to "software forges" (vcs + ci, etc). I love the idea of having a standard way of repos and CI such that everyone brings their own forge, builds their contribution out and upstreams.
- pjerem 4y ago
  I’d add that, even when you put aside everything you mentioned, GitHub isn’t even a good product to host your company’s code. It’s designed like a social network for open source stuff and it really shows in the UX. However, most companies uses GitHub to host their private repos and GitHub is pretty dumb at it. The core feature companies will use is Pull Requests but the implementation is garbage vs GitLab. The rest is either useless in corporate environment or not good enough. From my experience, GitHub is everywhere because founders used it by automatism and by the time you’d feel like you need an alternative, it’s too much pain to change anyway. I’ve never seen any company having any reason to and wanting to transition from something else (except from SVN) to GitHub.
3np 4y ago
You're looking at the per-repo settings of gitea there - obviously push-to-create doesn't fit there (; It's enabled for users/orgs via env vars ENABLE_PUSH_CREATE_USER/ENABLE_PUSH_CREATE_ORG. DEFAULT_PUSH_CREATE_PRIVATE sets whether new repos should be public or private (ideally this would be configurable by the user but oh well). https://docs.gitea.io/en-us/config-cheat-sheet/#repository-repository https://docs.gitea.io/en-us/config-cheat-sheet/#repository-r... If Codeberg doesn't have t enabled, maybe suggest they enable it?

codetrotter 4y ago

This page is not readable on my iPhone :( Here is a more readable version of that same page: https://archive.is/nRpOi#create-a-new-project-with-git-push https://archive.is/nRpOi#create-a-new-project-with-git-push

notpushkin 4y ago
Huh, that's weird – I've just checked and it looks fine on my Android, and in Safari in responsive design mode. :thinking:

smaudet 4y ago

I think this tool has merit where gh doesn't, in that it can/could integrate with other hosts. Github is a cancer on the git community - I know we tend to like "easy, fast, convenient" so mega-providers like GH or Gitlab are bound to occur, but we invariably find the downsides (centralized censorship, product placement, loss of features or random security vulns due to companies forgetting that the "simple" system is actually built on something complex) in the longterm. I'm not saying GH shouldn't exist, what would be even cooler is if a tool like wfh, in addition to pushing folders to github/gitlab, could push folders to arbitrary servers - if you own the domain/server and have the appropriate access, brand new git repo auto-hosted.

chiefalchemist 4y ago
Agreed. These platforms want you locked in. Having agnostic tools helps you sleep at night, and keep them more honest than they might be otherwise.
notpushkin 4y ago
It's not that bad actually, self-hosting is a thing – if you own the server, just set up your own Gitea or GitLab CE or something. I still prefer big instances myself though: most of my code is on GitLab.com, and some on Codeberg :-) Shameless plug: I'm working on a tool which lets you get Gitea (or anything else that can be run with a docker-compose) running on a server in a couple minutes. You can install it with a single curl | sh, then you get a nice panel in which you can paste your Compose file, make a couple tweaks and click Deploy. Gitea is actually the example app I picked for tutorial: https://lunni.dev/deploy/ https://lunni.dev/deploy/
vorpalhex 4y ago
There was an effort (though it seems to have died out) to bring federation to "software forges" (vcs + ci, etc). I love the idea of having a standard way of repos and CI such that everyone brings their own forge, builds their contribution out and upstreams.
pjerem 4y ago
I’d add that, even when you put aside everything you mentioned, GitHub isn’t even a good product to host your company’s code. It’s designed like a social network for open source stuff and it really shows in the UX. However, most companies uses GitHub to host their private repos and GitHub is pretty dumb at it. The core feature companies will use is Pull Requests but the implementation is garbage vs GitLab. The rest is either useless in corporate environment or not good enough. From my experience, GitHub is everywhere because founders used it by automatism and by the time you’d feel like you need an alternative, it’s too much pain to change anyway. I’ve never seen any company having any reason to and wanting to transition from something else (except from SVN) to GitHub.

3np 4y ago

You're looking at the per-repo settings of gitea there - obviously push-to-create doesn't fit there (; It's enabled for users/orgs via env vars ENABLE_PUSH_CREATE_USER/ENABLE_PUSH_CREATE_ORG. DEFAULT_PUSH_CREATE_PRIVATE sets whether new repos should be public or private (ideally this would be configurable by the user but oh well). https://docs.gitea.io/en-us/config-cheat-sheet/#repository-repository https://docs.gitea.io/en-us/config-cheat-sheet/#repository-r... If Codeberg doesn't have t enabled, maybe suggest they enable it?