tangled.org
This adds the functionality to auto-select a knot if there's only one configured (usually knot1.tangled.sh).
It also makes the knot selection required in the fork process just like in the repository creation process.
Monorepo for Tangled — https://tangled.org
appview/pages: auto-select knot when there's only one #836
merged
opened by
jordanreger.com
targeting
master
from
[deleted fork]:
master
expand 2 commits
hide 2 commits
0853638a
appview/pages: auto-select knot when there's only one
Signed-off-by: Jordan Reger <jordan@reger.co>
8154612a
appview/pages: make repo fork knot selection required
Signed-off-by: Jordan Reger <jordan@reger.co>
expand 1 commit
hide 1 commit
0853638a
appview/pages: auto-select knot when there's only one
Signed-off-by: Jordan Reger <jordan@reger.co>
removed the commit to make the knot radio button input required
boltless.me
shouldn't we just always auto-select the first knot?
anirudh.fi
@boltless.me I think this is fine, since we can then have a default knot selection in the user settings.
Yeah this is just a temporary fix. Default knot settings feels like a larger feature that needs discussion first
pull request successfully merged
fixes #300