You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -464,7 +464,7 @@ We assume in good faith that the information you provide is legally binding.
464
464
We adopted a release schedule to streamline the process of working on, finishing, and issuing releases. \
465
465
The overall goal is to make a major release every three or four months, which breaks down into two or three months of general development followed by one month of testing and polishing known as the release freeze. \
466
466
All the feature pull requests should be
467
-
merged before feature freeze. And, during the frozen period, a corresponding
467
+
merged before feature freeze. All feature pull requests haven't been merged before this feature freeze will be moved to next milestone, please notice our feature freeze announcement on discord. And, during the frozen period, a corresponding
468
468
release branch is open for fixes backported from main branch. Release candidates
469
469
are made during this period for user testing to
470
470
obtain a final version that is maintained in this branch.
Copy file name to clipboardExpand all lines: docs/content/contributing/guidelines-frontend.en-us.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,7 +47,7 @@ We recommend [Google HTML/CSS Style Guide](https://google.github.io/styleguide/h
47
47
9. Avoid unnecessary `!important` in CSS, add comments to explain why it's necessary if it can't be avoided.
48
48
10. Avoid mixing different events in one event listener, prefer to use individual event listeners for every event.
49
49
11. Custom event names are recommended to use `ce-` prefix.
50
-
12. Gitea's tailwind-style CSS classes use `gt-` prefix (`gt-relative`), while Gitea's own private framework-level CSS classes use `g-` prefix (`g-modal-confirm`).
50
+
12.Prefer using Tailwind CSS which is available via `tw-` prefix, e.g. `tw-relative`. Gitea's helper CSS classes use `gt-` prefix (`gt-df`), while Gitea's own private framework-level CSS classes use `g-` prefix (`g-modal-confirm`).
51
51
13. Avoid inline scripts & styles as much as possible, it's recommended to put JS code into JS files and use CSS classes. If inline scripts & styles are unavoidable, explain the reason why it can't be avoided.
0 commit comments