8000 Remove NMBS YAML import by joostlek · Pull Request #145733 · home-assistant/core · GitHub
[go: up one dir, main page]

Skip to content

Remove NMBS YAML import #145733

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 2, 2025
Merged

Remove NMBS YAML import #145733

merged 2 commits into from
Jun 2, 2025

Conversation

joostlek
Copy link
Member
@joostlek joostlek commented May 27, 2025

Proposed change

Remove NMBS YAML import

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

frenck
frenck previously requested changes May 27, 2025
Copy link
Member
@frenck frenck left a comment

Choose a reason for hiding this comment

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

Tests are failing.

../Frenck

@home-assistant home-assistant bot marked this pull request as draft May 27, 2025 17:57
@home-assistant
Copy link

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

@joostlek joostlek marked this pull request as ready for review May 27, 2025 18:05
@home-assistant home-assistant bot requested a review from frenck May 27, 2025 18:05
Copy link
Contributor
@silamon silamon left a comment

Choose a reason for hiding this comment

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

Please mark following issues/pull requests as fixed after merging in:

#136896
#136962

After the yaml import and migration an issue was found, and we decided not to fix it to not raise complexity. Since migration is about to removed, these issues and pull requests no longer needs to be reviewed or addressed.

@zweckj zweckj merged commit 434179a into home-assistant:dev Jun 2, 2025
34 checks passed
@joostlek joostlek deleted the nmbs-import branch June 2, 2025 13:11
@github-actions github-actions bot locked and limited conversation to collaborators Jun 3, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

several stations not imported in migration to NMBS config flow
4 participants
0