Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions .github/release-notes.md
Original file line number Diff line number Diff line change
@@ -1,11 +1,16 @@
---
version: 0.5.0
version: 1.0.0
---

# Forgejo GitHub Theme 0.5.0 - [Short subtitle]
# Forgejo GitHub Theme 1.0.0 - Forgejo 17, page by page

[1-2 sentence summary of the release.]
The theme now targets Forgejo 17, and most pages Forgejo has were compared against GitHub and brought in line: Actions,
project boards, settings, commits, branches, labels and milestones, notifications, the create pages and more. GitHub's
layouts are rendered by the templates instead of being patched in the browser, so pages no longer shift after they load.

# Compatibility

This release targets Forgejo `17`. It was tested against Forgejo `17.0.0`, including the bundled template overrides.

The templates are bound to Forgejo 17's template data. On Forgejo 16 keep using 0.4.0; install this release together
with the upgrade to Forgejo 17, stylesheets and templates at the same time.
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ is written for the people who install the theme, so the title and the label deci

Areas: `Actions`, `Auth`, `Branches`, `Code`, `Commits`, `Dashboard`, `Editor`, `Explore`, `Forks`, `Forms`, `Insights`,
`Issues`, `Labels`, `Milestones`, `Navbar`, `Notifications`, `Organizations`, `Packages`, `Profile`, `Projects`,
`Pull requests`, `Releases`, `Repository`, `Settings`, `Teams`, `Themes`.
`Pull requests`, `Releases`, `Repository`, `Settings`, `Teams`, `Templates`, `Themes`.

Reuse an existing area whenever one fits; add a new area only for a page people recognise by that name, and add it to
this list in the same pull request. Never use file, component or style names as an area.
Expand Down
Loading