docs: remove stray status key from netlify.toml [build] table - #1336
Open
codyjlandstrom wants to merge 1 commit into
Open
docs: remove stray status key from netlify.toml [build] table#1336codyjlandstrom wants to merge 1 commit into
codyjlandstrom wants to merge 1 commit into
Conversation
The final [build] table carried a status = 301 line left over from a [[redirects]] entry. status is not a valid key in Netlify's [build] table, so it was ignored, but it read as a misconfiguration. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: Cody Landstrom <cody@okteto.com>
codyjlandstrom
requested review from
ifbyol,
pchico83 and
rlamana
as code owners
August 26, 2026 19:17
✅ Deploy Preview for okteto-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
ifbyol
approved these changes
Aug 27, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What
Removes a stray
status = 301line from the final[build]table innetlify.toml.statusis not a valid key in Netlify's[build]table — it was silently ignored, but it read as a copy-paste remnant from a[[redirects]]entry.Verification
Parsed the full file with a TOML parser after the change: all 170
[[redirects]]blocks use only valid keys (from,to,status, oneforce), and the[[headers]]table is well-formed. No other table has misplaced keys.🤖 Generated with Claude Code