Our next notification will be after the GitHub cutoff. We will continue
to look at projects in the feature flag to see which ones now have an
integration configured. Two more notification rounds is probably
warranted.
This does a number of things:
* Removes the simple_search endpoint, so that we only have 1 entry point for search
* Re-adds the search signals that we removed in the refactor, these are required for the .com
* A few small UI/UX cleanup things to make search results nicer
* Notify users about the usage of deprecated webhooks
Each time a deprecated webhook is hit, a notification is
created (without duplicating it) to be sent.
* Extend notification to support de-dup and delayed email sent
* Improve decorator to support generic and specific VCS webhook views
* Remove no necessary settings
* DeprecatedWebhookEndpointNotification tests and improvements
* Better docstring
* Lint
* Update copy on notifications for github services deprecation (#5067)
* Updated copy on webhooks
* Drop "deprecated webhook endpoint" copy, this is core team nomenclature, not user
nomenclature.
* Add small amount of docs to point to
* Update docs and point to docs in notification message
* Add year
* Split up deprecated view notification to GitHub and other webhook endpoints (#5083)
* Updated copy on webhooks
* Drop "deprecated webhook endpoint" copy, this is core team nomenclature, not user
nomenclature.
* Add small amount of docs to point to
* Update docs and point to docs in notification message
* Split up deprecated view notification to GitHub and other webhook endpoints
This sets a date for deprecated of these endpoints as Mar 1st 2019. Too
soon?
* Reduce complexity and drop decorator pattern for Notification
classmethod pattern used in other notifications
* Add notifications for non-GitHub incoming webhooks
* Add docs as well
* More renaming and slight refactor
Found out 2x messages are being generated, so this stops the automated
mechanism for triggering these messages.
* Update dates
* Also update docs
* Typo on date
* Back out some more of the changes to notifications to make them operable without automation
* Add admin method for notification
* Add admin filter for project features
We are using the same 404.html template for 404 errors when serving
documentation (.io) and also on our platform (.org).
The Login/Logout button only shows the proper word when the 404 page
comes from .org, but it always says "Login" when we hit .io 404 pages.
As this is only confusing and there is not value added here, I'm
removing it completely.
This is confusing for users who don't know what a slug is.
We never show the slug to folks,
so when we use it in documentation they don't know what it is.
Maksudul Haque
Manuel Kaufmann
Eric Holscher
Anthony
dojutsu-user
Eric Holscher
bansalnitish
Santos Gallegos
Rahul Tiwari
Philipp Bräutigam