Skip to content

Update submit.planning.data.gov.uk to provide.planning.data.gov.uk - #1056

Merged
DilwoarH merged 1 commit into
mainfrom
1022-update-providers-service-urls
Jun 18, 2025
Merged

Update submit.planning.data.gov.uk to provide.planning.data.gov.uk#1056
DilwoarH merged 1 commit into
mainfrom
1022-update-providers-service-urls

Conversation

@DilwoarH

@DilwoarH DilwoarH commented Jun 18, 2025

Copy link
Copy Markdown
Contributor

What type of PR is this? (check all applicable)

  • Refactor
  • Feature
  • Bug Fix
  • Optimization
  • Documentation Update

Description

Update submit.planning.data.gov.uk to provide.planning.data.gov.uk

Related 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.

  • Yes
  • No, and this is why: Please replace this line with details on why tests have not been included
  • I need help with writing tests

QA sign off

  • Code has been checked and approved
  • Design has been checked and approved
  • Product and business logic has been checked and proved

[optional] Are there any post-deployment tasks we need to perform?

[optional] Are there any dependencies on other PRs or Work?

Summary by CodeRabbit

  • Chores
    • Updated service URLs from "submit.planning.data.gov.uk" to "provide.planning.data.gov.uk" across all environments and in the privacy notice.
    • Simplified the pull request template by removing redundant sections and preview link instructions.

@DilwoarH DilwoarH linked an issue Jun 18, 2025 that may be closed by this pull request
3 tasks
@coderabbitai

coderabbitai Bot commented Jun 18, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

This 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

Files Change Summary
config/default.yaml, config/development.yaml, config/production.yaml, config/staging.yaml Updated the url value from 'submit.planning.data.gov.uk' to 'provide.planning.data.gov.uk' in all environments.
src/views/privacy-notice.html Changed service URL reference from 'submit.planning.data.gov.uk' to 'provide.planning.data.gov.uk'.
.github/PULL_REQUEST_TEMPLATE.md Removed preview link section and duplicate description; deleted commented ticket/issue lines.

Assessment against linked issues

Objective Addressed Explanation
Update all service URLs from 'submit.planning.data' to 'provide.planning.data' (#1022)
Put redirects in place from 'submit' to 'provide' URLs (#1022) No evidence of redirect implementation in the code changes.
Agree if existing redirects will also be redirected or not, and review user access via old URLs (#1022) No code changes address this; unclear if discussion or analytics are handled elsewhere.

Assessment against linked issues: Out-of-scope changes

Code Change (file_path) Explanation
Pull request template simplification (.github/PULL_REQUEST_TEMPLATE.md) The linked issue is solely about service URL updates and redirects; template changes are unrelated.

Possibly related PRs

Suggested reviewers

  • rosado

Poem

A hop, a skip, a URL switch,
From "submit" to "provide"—a seamless pitch!
Configs align, the notice is clear,
Templates trimmed for reviewers here.
🐇 With every change, we bound ahead,
To "provide" the future—enough said!


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.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need 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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions

Copy link
Copy Markdown

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 66.51% 5955 / 8953
🔵 Statements 66.51% 5955 / 8953
🔵 Functions 65.37% 253 / 387
🔵 Branches 79.22% 759 / 958
File CoverageNo changed files found.
Generated in workflow #1076 for commit 093f233 by the Vitest Coverage Report Action

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
config/default.yaml (1)

18-18: Domain updated correctly, but review ToDo comment and slash consistency
The url has been updated to https://provide.planning.data.gov.uk. Consider removing the now-stale # ToDo: url and name might need updating comment 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

📥 Commits

Reviewing files that changed from the base of the PR and between 57f9eb4 and 093f233.

📒 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
The url value has been updated to https://provide.planning.data.gov.uk/, matching the intended production endpoint.

config/staging.yaml (1)

13-13: Domain update applied correctly
The url value has been updated to https://provide.staging.planning.data.gov.uk/, aligning with the staging environment.

config/development.yaml (1)

14-14: Domain update applied correctly
The url value has been updated to https://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.

@DilwoarH
DilwoarH merged commit 5b07ee2 into main Jun 18, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update providers service URLs

2 participants