Update development instructions #96
Labels
No Label
dependencies
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
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/theme#96
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
The current development instructions could need some more information showcasing the shortest way to make a change in the theme and see a preview of the website.
I'll outline my way for the most recent PR which feels quite unintutive. If there are other ways, we should note them down :)
src/main.scss
npm run watch
to rebuild the theme (includingstatic/styles/main.css
which is the one which will trigger a change in the website later ondocs/themes/gitea
)make server
orhugo server
and observe the changesWhile the "copy to local checkout" is tricky as local paths are involved, I was wondering if we should suggest to checkout this repo as a git repo within
gitea
.This would remove the need for step (3) - but maybe there are better ways?
Another option could be to have Netlify Pull Request previews, i.e. netlify renders Gitea.io with the theme resources from the pull request and displays a live-preview of the changes with a dummy URL in the PR.
I have two other hugo-based blogs running this way and like this setup a lot.
Let me know if I can help.