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
It'd be useful to have a summary of user-visible changes between each release documented on Github releases tab and AMO page. Also, 2.1.0 is there on AMO, but not on Github releases tab.
The text was updated successfully, but these errors were encountered:
@jonathanKingston@princiya As mentioned above by @rathann, the v2.1.0 is not documented on GitHub release yet while the cloned repo is apparently working on v2.1.0 . Also, @rathann I think I can help here. Please explain this issue to me in more detail so that I can attempt to fix this, although I am not sure if this a programmatic change or something that is done manually by authorized people regularly.
@Parikshit-Hooda If you follow a strict convention for commit messages and tag user-visible changes, you can generate release notes automatically. I don't think you do that in this project, so the only option would be to do this manually for every release. I'm not sure what more you want me to explain.
It'd be useful to have a summary of user-visible changes between each release documented on Github releases tab and AMO page. Also, 2.1.0 is there on AMO, but not on Github releases tab.
The text was updated successfully, but these errors were encountered: