remove trailing whitespace from deployment/README.md #171
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
ambition
application-offering
ambition
configure-applications
ambition
front-end
ambition/install-applications
ambition
security
ambition
switch-host
ambition
update-applications
ambition
user-management
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
3 participants
fricklerhandwerk
lois
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
fediversity/fediversity!171
Loading…
Reference in a new issue
No description provided.
Delete branch "kiara/fediversity:rm-trailing-whitespace"
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?
$(git log --pretty=%s | head -n 1)to remove trailing whitespace from deployment/README.mdlgtm
I'm curious - do we know how it got there in the first place?
@Niols: tl;dr it's on me.
going by the commit list, the first offending commit was the merge of #166, whereas that PR originally showed a green CI.
i believe that one went bad since rebasing on
142af8d0ee, while yours truly turned out too impatient to await CI rerunning after a rebase on what seemed an innocuous PR that had seemed green already./cc @fricklerhandwerk
Ah yes, fair enough. I don't think it's on you, I think it's on branch protection rules not doing their job here; you shouldn't be able to merge a PR where CI isn't green without checking a big “I UNDERSTAND THE RISKS” box.
i did check such a box 🙈
Hehe, nevermind then!
If you're using the dev environment from the flake, it should also prevent you from making such commits in the first place.