Update submit.planning.data.gov.uk to provide.planning.data.gov.uk - #1056
Conversation
WalkthroughThis update modifies service URLs across configuration files and the privacy notice, changing them from 'submit.planning.data.gov.uk' to 'provide.planning.data.gov.uk'. The pull request template was also streamlined by removing the preview link section and redundant description fields. Changes
Assessment against linked issues
Assessment against linked issues: Out-of-scope changes
Possibly related PRs
Suggested reviewers
Poem
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Coverage Report
File CoverageNo changed files found. |
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
config/default.yaml (1)
18-18: Domain updated correctly, but review ToDo comment and slash consistency
Theurlhas been updated tohttps://provide.planning.data.gov.uk. Consider removing the now-stale# ToDo: url and name might need updatingcomment above, and decide whether to add a trailing slash here for consistency with other environment configs..github/PULL_REQUEST_TEMPLATE.md (1)
17-17: Improve placeholder guidance.Refine the placeholder to prompt for a concise summary and rationale, e.g.:
_Please provide a concise overview of what this PR changes and why._
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (6)
.github/PULL_REQUEST_TEMPLATE.md(1 hunks)config/default.yaml(1 hunks)config/development.yaml(1 hunks)config/production.yaml(1 hunks)config/staging.yaml(1 hunks)src/views/privacy-notice.html(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: run-tests / test
🔇 Additional comments (5)
config/production.yaml (1)
13-13: Domain update applied correctly
Theurlvalue has been updated tohttps://provide.planning.data.gov.uk/, matching the intended production endpoint.config/staging.yaml (1)
13-13: Domain update applied correctly
Theurlvalue has been updated tohttps://provide.staging.planning.data.gov.uk/, aligning with the staging environment.config/development.yaml (1)
14-14: Domain update applied correctly
Theurlvalue has been updated tohttps://provide.development.planning.data.gov.uk/, reflecting the development environment change.src/views/privacy-notice.html (1)
12-12: Privacy notice domain reference updated
The service link text and href have been updated to[provide.planning.data.gov.uk](https://provide.planning.data.gov.uk), matching the new domain..github/PULL_REQUEST_TEMPLATE.md (1)
15-15: Description header placement is clear.Moving the Description section to the top and removing redundancy enhances readability.
What type of PR is this? (check all applicable)
Description
Update
submit.planning.data.gov.uktoprovide.planning.data.gov.ukRelated Tickets & Documents
QA Instructions, Screenshots, Recordings
Before
Before screenshot here
After
After screenshot here
Added/updated tests?
We encourage you to keep the code coverage percentage at 80% and above.
QA sign off
[optional] Are there any post-deployment tasks we need to perform?
[optional] Are there any dependencies on other PRs or Work?
Summary by CodeRabbit