Move now-and-next feed to /schedule/ #1739
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Jonty
force-pushed
the
move-now-next-feed-path
branch
from
417a32d
to
8c6432a
Compare
Our docs say now-and-next.json lives under /schedule/ but it is actually in the root. All our other feeds are in /schedule/ so we should just move it there for consistency - this won't break anything now as the feed returns nothing between events anyway.
Jonty
force-pushed
the
move-now-next-feed-path
branch
from
8c6432a
to
5995df3
Compare
marksteward
approved these changes
Jun 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our docs say now-and-next.json lives under /schedule/ but it is actually in the root. All our other feeds are in /schedule/ so we should just move it there for consistency - this won't break anything now as the feed returns nothing between events anyway.