Skip to content

[Simplified Actions] Add Primary and Secondary actions to report previews and header #59960

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

Closed
28 tasks
luacmartins opened this issue Apr 9, 2025 · 5 comments
Closed
28 tasks
Assignees
Labels
Engineering Reviewing Has a PR in review Weekly KSv2

Comments

@luacmartins
Copy link
Contributor

luacmartins commented Apr 9, 2025

cc @jnowakow @borys3kk @mananjadhav @suneox let's use this issue to tackle the implementation of the primary and secondary actions to the report previews and headers, e.g. what this PR implemented and later reverted, while taking into account all the blockers that were reported:

@luacmartins
Copy link
Contributor Author

I think as a first step, we can revert the revert PR and then start tackling each of the issues above. Some of them already have solutions.

Copy link

melvin-bot bot commented Apr 24, 2025

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

@flaviadefaria flaviadefaria moved this to Second Cohort - CRITICAL in [#whatsnext] #migrate Apr 28, 2025
Copy link

melvin-bot bot commented Apr 29, 2025

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

@melvin-bot melvin-bot bot added Weekly KSv2 and removed Weekly KSv2 labels Apr 29, 2025
Copy link

melvin-bot bot commented Apr 29, 2025

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

@luacmartins
Copy link
Contributor Author

I'm gonna close this issue in favor of the latest tracking issue here - #60852

@github-project-automation github-project-automation bot moved this from Second Cohort - CRITICAL to Done in [#whatsnext] #migrate Apr 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Engineering Reviewing Has a PR in review Weekly KSv2
Projects
Development

No branches or pull requests

5 participants