shift-org / shift-org/shift-docs
remove any legacy redirects that are no longer needed
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 30
- Forks
- 25
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
- in netlify.toml
- and in nginx config (do we need any
/legacyor/backenddetails?)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the redirects in netlify.toml and the nginx configuration, focusing on any /legacy or /backend entries. Confirm which redirects are still required before removing obsolete ones; done means both configurations retain only needed redirects and no longer reference unnecessary legacy routes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100