alpha
Login
or
Join now
tangled.org
/
core
Star
2
Fork
66
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Monorepo for Tangled
tangled.org
Star
2
Fork
66
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Overview
Issues
11
Pulls
25
Pipelines
core
/
appview
/
validator
/
at
dwn/spindle-microvm-debugssh
9 files
Lewis
appview: read permissions thru knotacl service
2w ago
bc598317
issue.go
appview: read permissions thru knotacl service Lewis: May this revision serve well! <lewis@tangled.org>
2 weeks ago
label.go
appview: read permissions thru knotacl service Lewis: May this revision serve well! <lewis@tangled.org>
2 weeks ago
label_test.go
appview: read permissions thru knotacl service Lewis: May this revision serve well! <lewis@tangled.org>
2 weeks ago
patch.go
appview: improve patch validation automatically adds a newline to patches that are missing one.
8 months ago
pull.go
appview/validator: write validators for pull records Signed-off-by: oppiliappan <me@oppi.li>
4 months ago
repo_topics.go
appview: add website and topics fields to repo Removed description edit UI / endpoints and put unified base settings form in repository settings page. This form is restricted to `repo:owner` permission same as before. The internal model of topics is an array but they are stored/edited as single string where each topics are joined with whitespaces. Having a dedicated topics table with M:M relationship to the repo seems a bit overkill considering we will have external search indexer anyway. Signed-off-by: Seongmin Lee <git@boltless.me>
7 months ago
string.go
appview/models: move db.String into models Signed-off-by: oppiliappan <me@oppi.li>
9 months ago
uri.go
appview: add website and topics fields to repo Removed description edit UI / endpoints and put unified base settings form in repository settings page. This form is restricted to `repo:owner` permission same as before. The internal model of topics is an array but they are stored/edited as single string where each topics are joined with whitespaces. Having a dedicated topics table with M:M relationship to the repo seems a bit overkill considering we will have external search indexer anyway. Signed-off-by: Seongmin Lee <git@boltless.me>
7 months ago
validator.go
appview: read permissions thru knotacl service Lewis: May this revision serve well! <lewis@tangled.org>
2 weeks ago