RNS Logo

rns.recipes

◈ 9ce92808be498e9e05590ff27cbfdfe4

rngit pages issue

Started by Gwyn 4b3c228d104c261f... ·

Gwyn a44f3aefb2f6777b...
#1

First, thank you to everyone involved with Reticulum. It's excellent. :)
Second, if this thread is in the wrong category, please let me know and I can report elsewhere. After reading everyhing I could get my hands on, this seemed the most productive place for this question.

 

In the process of setting up rngit and importing a repo, I discovered that browsing the repo doesn't work entirely as expected if the default branch isn't 'master'. I'm working through the pages.py and server.py code, which so far looks like it should be doing the right thing.

 

I'll post here if I arrive at a fix but this way if others are hitting this we can collaborate.

 

I'd also like to be able to choose the default branch of new repositories, ideally in the config file globally, and on the command line for individual repos, or even maybe by group, but these are all larger decisions that might have ripple effects.

 

Anyway, thank you, and happy to test any suggestions others might have.

bergie f9477df559d52317...
#2

It is a little bit annoying that we can't change the default branch to main, but anyway, you can fix it per-repo by going to the repo's folder on the rngit server and running:

 

git symbolic-ref HEAD refs/heads/main
Gwyn a44f3aefb2f6777b...
#3

True. And it retains whatever the default branch is on imported repos.

Post a Reply

Supports Markdown: **bold**, *italic*, `code`, ```code blocks```, [links](url)

Log in to upload images

Quote
Copied to clipboard