fix relative path computation #38
No reviewers
Labels
No labels
0 points
0.5 points
1 point
13 points
2 points
21 points
3 points
34 points
5 points
55 points
8 points
api service
blocked
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
infinite points
productisation
project-management
question
role: application developer
role: application operator
role: hosting provider
role: maintainer
security
technical debt
testing
type unclear
type: bug
type: deliverable
type: key result
type: objective
type: task
type: user story
user experience
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: fediversity/fediversity#38
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fricklerhandwerk/Fediversity:fix-nav-bug"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
this unbreaks navigation in nested pages
If there are tests, should CI run them?
Also, the CI could try to build the website, just to check that that does work. In the far future, we can imagine going for CD of the website from the CI pipeline, but for now that would be a start.
Yes, absolutely, tests and builds should be run in CI.