GIT - Github, Gitea, Gitlabs. Everything git

!everything_git

@lemmy.ml
Create post
How to manual download GitHub Packages files (wget, curl)

How to manual download GitHub Packages files (wget, curl)

Open link in next tab

https://tech.michaelaltfield.net/2024/09/03/container-download-curl-wget/

[solved] best way to grant access to a single repository?

[solved] best way to grant access to a single repository?

hello! For University I need to use a remote machine with a very very VERY weak password I cannot change, and I have to use that machine to edit some code with a few other students of my team. All the code should then be pushed to a repo of my personal github. I'd like to be able to grant access to only that repo, so that if someone guesses the password it cannot touch my other stuffs. What options do I have?

[SOLVED] EDIT:
as suggested by @elliot_crane@lemmy.world I created a github fine grained access token setting its only permission as read/write only that repo. Then I cloned the repo on the remote machine and set the url to include the token:

git remote set-url origin https://myusername:MYTOKEN@github.com/myusername/myrepo.git 

I then set the user and email:

git config user.name myusername
git config user.email my@email.com

and voilà! I can now simply push without any password requested! And in case someone gained access to the token (that is stored in plain text inside the .git folder) it would only grant access to that specific repo, limiting the damages

What exactly is Codeberg's relation to Forgejo?

What exactly is Codeberg's relation to Forgejo?

As far as I understand it, Forgejo is a soft-fork of Gitea, and, as far as I am aware, Gitea includes both the backend and frontend. But then I came across Codeberg, which appears to state:

Self-Hosting Forgejo, the software that powers Codeberg.

This makes it sound like Forgejo is the backend, and Codeberg is the frontend, but I'm not 100% sure. If so, did Forgejo separate Gitea's UI, and just soft-fork the backend?

Removing "Releases" and "Packages" section from GitHub repository's page

Removing "Releases" and "Packages" section from GitHub repository's page

Can you not remove "Releases" and "Packages" section from your repository in GitHub?

There is a gear icon on the repository page "Edit repository details" and it seemingly allows you to remove those sections from the page but they don't do anything. Is it just me / is this limited with a free account or just a bug?

Couldn't find anything about this by googling. Any answers much appreciated!

[repost] Best GitHub Alternative?

[repost] Best GitHub Alternative?

My account was flagged because I forked and contributed to the project Eaglercraft, and that means my account is basically useless. I have had enough of Microsoft's exploitation of power and want to switch to another alternative.

I tried GitLab, but I need to signup with a credit card and I am not comfortable giving my personal info out.
I tried Gitea and the experience is great, but I am limited to 5 repos. I tried Source Forge, but I cannot verify my phone number when creating a repo. The prompt just returns an API error.

What other alternative should I try?

Git man page generator
Open link in next tab

Git man page generator

https://git-man-page-generator.lokaltog.net/

Create an infinite amount of straightforward and readable git manual pages.

Open Letter to Gitea
Open link in next tab

The Gitea Community is asking Gitea Owners to correct conflicts of interest and restore Community Trust.

https://gitea-open-letter.coding.social/

The Gitea Community is asking Gitea Owners to correct conflicts of interest and restore Community Trust.

I hate squash merges
Open link in next tab

I hate squash merges

https://beyermatthias.de/i-hate-squash-merges

End of last year, I published the article "I hate conventional commits". I received a lot of good feedback on this article and it was eve...

I hate squash merges
How to maintain a fork of an evolving project while local changes are minimal and mostly related to making project work in personal platform

How to maintain a fork of an evolving project while local changes are minimal and mostly related to making project work in personal platform

So I have this exact need:

There is an upstream project doing their own thing over git and I want to build container images locally and commit them to my image repository all while following the same version system as upstream.

To be more precise (perhaps abstract) about my need, what is the best way to apply the same patch when upstream release a new version.

Any input and best practices or lessons learned are welcome.