this post was submitted on 24 Jan 2025
31 points (100.0% liked)

Programming

17981 readers
212 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 2 years ago
MODERATORS
snowe
Ategon
[email protected]
31
sourcehut is super confusing (self.programming)
submitted 6 days ago by verstra to c/programming
17 comments fedilink hide all child comments
 

Anyone using soucehut (sr.ht)? Can you please explain to me how you navigate the site?

I really like the minimalist approach and extremely fast website UI, but I just cannot navigate the site.

If I'm looking at source of a repo on https://git.sr.ht/ and want to see open tickets, how do I navigate to https://todo.sr.ht/ ? If I click on "todo" at the top, it takes me to my todo lists, not todo of the project I was just looking at.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 6 points 5 days ago (1 children)

Create a new repo locally.

git init
git add .
git commit -m "Initial commit"

Then to create a new remote repo, you can do this.

git remote add origin [email protected]:~user/my-new-repo
git push origin main

You'll get a message that says.

remote: 
remote:         NOTICE
remote: 
remote:         You have pushed to a repository which did not exist. ~user/my-new-repo
remote:         has been created automatically. You can re-configure or delete this
remote:         repository at the following URL:
remote: 
remote:         https://git.sr.ht/~user/my-new-repo/settings/info
[โ€“] [email protected] 1 points 5 days ago* (last edited 5 days ago)

You forgot a small detail.

Afaik you can not change repo visibility this way (without using the web UI or the GraphQL API). So if the goal is to avoid the web UI you'd have to add a step (which you can read up on in the script I shared).

Same for the repo description (but maybe there is a git native way, idk).

Great write up otherwise, thank you!