Skip to content
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

fix(azure-devops): corrected api report #1871

Merged

Conversation

christoph-jerolimov
Copy link
Member

@christoph-jerolimov christoph-jerolimov commented Nov 6, 2024

Hey, I just made a Pull Request!

Hey @awanlin, maybe you have doing something similar in the same moment... Just wanted help.

Updated the API Report as it was missed in #1805 due to not being rebased after #1803 was merged which fixed an issue caused by backstage/backstage#27551

It doesn't include a changeset because its included in yours and the release PR will be stuck until this gets in.

Hope that helps.

✔️ Checklist

  • A changeset describing the change and affected packages. (more info)
  • Added or updated documentation
  • Tests for new functionality and regression tests for bug fixes
  • Screenshots attached (for UI changes)
  • All your commits have a Signed-off-by line in the message. (more info)

@christoph-jerolimov christoph-jerolimov self-assigned this Nov 6, 2024
@christoph-jerolimov christoph-jerolimov requested review from awanlin and a team as code owners November 6, 2024 15:49
@backstage-goalie
Copy link
Contributor

Missing Changesets

The following package(s) are changed by this PR but do not have a changeset:

  • @backstage-community/plugin-azure-devops

See CONTRIBUTING.md for more information about how to add changesets.

Changed Packages

Package Name Package Path Changeset Bump Current Version
@backstage-community/plugin-azure-devops workspaces/azure-devops/plugins/azure-devops none v0.6.1

@awanlin
Copy link
Contributor

awanlin commented Nov 6, 2024

Hi @christoph-jerolimov, good catch and thanks for the PR. Please do not merge this, I specific reasons for doing this migration and would like to handle it on my own to fully understand what went wrong and make sure that's included in my documentation. When I'm ready I'll follow up.

Copy link
Contributor

@awanlin awanlin left a comment

Choose a reason for hiding this comment

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

Please do not merge until I have explicitly approved, thanks 👍

Copy link
Contributor

@awanlin awanlin left a comment

Choose a reason for hiding this comment

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

OK, figured this out, got surprised initially as I thought this was a MUI v5 migration issue but this is in the API Reports. The issue comes from two places - partly myself for not rebasing the branch once #1803 was merge and partly due to this bug.

Can we update the PR title to this:

Azure DevOps - Corrected API Report

And then in the description put a note like this:

Updated the API Report as it was missed in #1805 due to not being rebased after #1803 was merged which fixed an issue caused by backstage/backstage#27551

Also, totally fine with not having a changeset, that makes sense to me 👍

@christoph-jerolimov christoph-jerolimov changed the title Azure DevOps - Migrated to MUI v5 - #1805 follow-up Azure DevOps - Corrected API Report Nov 7, 2024
@christoph-jerolimov
Copy link
Member Author

christoph-jerolimov commented Nov 7, 2024

Rebased and updated the commit message, PR title and first PR comment

Signed-off-by: Christoph Jerolimov <jerolimov+git@redhat.com>
@christoph-jerolimov christoph-jerolimov changed the title Azure DevOps - Corrected API Report fix(azure-devops): corrected api report Nov 7, 2024
Copy link
Contributor

@awanlin awanlin left a comment

Choose a reason for hiding this comment

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

Thanks again @christoph-jerolimov 🚀

@awanlin awanlin merged commit 1fbf57e into backstage:main Nov 7, 2024
11 checks passed
@christoph-jerolimov christoph-jerolimov deleted the fix-azure-devops-release branch November 7, 2024 22:22
awanlin added a commit to awanlin/community-plugins that referenced this pull request Nov 28, 2024
awanlin added a commit to awanlin/community-plugins that referenced this pull request Nov 28, 2024
This reverts commit 1fbf57e.

Signed-off-by: Andre Wanlin <awanlin@spotify.com>
awanlin added a commit that referenced this pull request Nov 29, 2024
* Revert "Azure DevOps - Migrated to MUI v5 (#1805)"

This reverts commit c5283ca.

Signed-off-by: Andre Wanlin <awanlin@spotify.com>

* Revert "fix(azure-devops): corrected api report (#1871)"

This reverts commit 1fbf57e.

Signed-off-by: Andre Wanlin <awanlin@spotify.com>

* Added changeset

Signed-off-by: Andre Wanlin <awanlin@spotify.com>

---------

Signed-off-by: Andre Wanlin <awanlin@spotify.com>
CryptoRodeo pushed a commit to CryptoRodeo/community-plugins that referenced this pull request Dec 10, 2024
* Revert "Azure DevOps - Migrated to MUI v5 (backstage#1805)"

This reverts commit c5283ca.

Signed-off-by: Andre Wanlin <awanlin@spotify.com>

* Revert "fix(azure-devops): corrected api report (backstage#1871)"

This reverts commit 1fbf57e.

Signed-off-by: Andre Wanlin <awanlin@spotify.com>

* Added changeset

Signed-off-by: Andre Wanlin <awanlin@spotify.com>

---------

Signed-off-by: Andre Wanlin <awanlin@spotify.com>
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.

2 participants