-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
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
Score Limit stopped working #46
Comments
Shoot. I merged a breaking change last night that renamed the field to scoreLimit would it be hard to change the urls of your feed to use the new name or I can revert to give everyone time to move over? In the future I wonder what a good way would be to communicate with the people that use this feed before changing stuff. 🤔 |
Ah no worries I'll change my feed, thanks a lot for all the work! I'll head to this repo as soon as I notice any breaks like today - so maybe if you put a section in the README about recent breaking changes and how the users can adapt could be good? :) |
Like the other user said, I think mentioning breaking changes prominently on the README here for a while should be fine. This GitHub repo is where every user of the application and the instance you host will come for support, and the people who still use the service (and the rate limit) will definitely come here in the next couple days when they notice the issue; and all issues going forward. |
Perhaps you could enable "Releases" for this repo, because people can then subscribe to those and will get notified of new versions / changelogs automatically. Random example: https://github.com/go-gitea/gitea/releases and then click |
so many broken feeds...🥲 |
💥 #47 You can now follow |
The score limit stopped working around 10 or so hours ago and all posts are coming into the feed unfiltered.
The text was updated successfully, but these errors were encountered: