Use gitea org as default author #233
Labels
No Label
in progress
kind/bug
kind/deployment
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
kind/question
kind/security
kind/testing
kind/translation
kind/ui
lgtm/done
lgtm/need 1
lgtm/need 2
priority/critical
priority/low
priority/maybe
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
status/blocked
status/needs-feedback
status/wip
No Milestone
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/blog#233
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "jolheiser/blog:authors"
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?
Or maybe something like "The Gitea maintainers" or "The Gitea core group"? Sounds a bit more "human" than just "Gitea".
Yes, but this value is currently used as a fallback for author in the string
https://gitea.com/<author>
Alternatively, I could open another PR against
theme
to not fallback, but rather use something else entirely.The current problem, as I mentioned above, is that this value is only used in the concat string
https://gitea.com/{{ .Params.author | default .Site.Params.author }}
One resolution is this PR, as it means it resolves to
https://gitea.com/Gitea
An alternative could be that it does more explicit checking instead of using a default, such that
{{ if not .Params.author }}...{{ end }}
and we can instead put a more suitable default like you proposed.This is just a Hugo think in the end, isn't it? It feels like there must be an "easy" solution to have "proper names" including whitespaces etc as the author with a smart logic for the respective URL insertion? ?
But for now - it should not block the current blog post.
Yeah, it's all something we can control, just not sure how to get the best result without breaking past assumptions etc.