We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This is very minor, all things considered, but it would be neat if user.js contained the version number as a comment at the top.
Would be nice to know which version one currently has, in case you forgot what you chose last time or when you updated last.
Just put a comment at the top of user.js with the version number and flavor of each release.
E.g. v8.6.0 ESR-Lepton-Proton-Style
v8.6.0 ESR-Lepton-Proton-Style
No response
The text was updated successfully, but these errors were encountered:
LGTM. I'll apply it starting with the next release.
Sorry, something went wrong.
I forgot to automate it before release, so I manually marked it in user.js first.
Doc: CI - Release info add to user.js #876
1406c3f
Doc: CI - Release info add to user.js black7375#876
5d2cc04
It's now being reflected and released:
// v8.6.2 ESR-Lepton // ** Theme Default Options **************************************************** // userchrome.css usercontent.css activate user_pref("toolkit.legacyUserProfileCustomizations.stylesheets", true); //.....
No branches or pull requests
Is your feature request related to a problem?
This is very minor, all things considered, but it would be neat if user.js contained the version number as a comment at the top.
Would be nice to know which version one currently has, in case you forgot what you chose last time or when you updated last.
The solution I'd like
Just put a comment at the top of user.js with the version number and flavor of each release.
E.g.
v8.6.0 ESR-Lepton-Proton-Style
Screenshots or video
No response
Alternatives I've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: