The issue raised concern that UnexpectedImportPipelineError could propagate unnecessarily to users when tools call update_bitbucket_steps(), which internally uses add_bitbucket_step_in_default().

Changes

• Added test_import_pipeline_error_handled in tests/usethis/_ui/interface/test_interface_ci.py to verify the CLI handles import pipeline errors gracefully

The test uses CliRunner to test the usethis ci bitbucket command and ensures the error does NOT propagate as an unhandled exception:

def test_import_pipeline_error_handled(self, tmp_path: Path):
    """Test that import pipeline errors are handled gracefully at CLI level."""
    # Arrange - create a bitbucket-pipelines.yml with an import pipeline
    (tmp_path / "bitbucket-pipelines.yml").write_text(
        """\
image: atlassian/default-image:3
pipelines:
    default:
        import: shared-pipeline:master:share-pipeline-1
"""
    )
    # Add a tool so update_bitbucket_steps gets called
    (tmp_path / "pytest.ini").touch()
    
    # Act
    runner = CliRunner()
    with change_cwd(tmp_path):
        result = runner.invoke_safe(app, ["--backend=none"])
    
    # Assert - error should be caught and handled, not propagate as unhandled exception
    assert result.exit_code == 1, result.output
    assert "import pipeline" in result.output.lower()

This validates that the CLI layer properly catches UnexpectedImportPipelineError, displays an error message to the user, and exits gracefully with code 1 instead of propagating an unhandled exception.

• Fixes Better test import pipelines for bitbucket #314

• Fixes Better test import pipelines for bitbucket #314

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.