Skip to content

refactor: move material.aio GHA to the root #30288

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 4 commits into from
Jan 14, 2025
Merged

Conversation

alexeagle
Copy link
Contributor

This makes them functional again. To keep this change simple, we just update the working directory but run the same things

@alexeagle alexeagle requested review from a team as code owners January 8, 2025 15:35
@alexeagle alexeagle requested review from crisbeto and amysorto and removed request for a team January 8, 2025 15:35
This makes them functional again. To keep this change simple, we just update the working directory but run the same things
@alexeagle alexeagle force-pushed the mai-ci branch 2 times, most recently from 4415539 to 58bd39a Compare January 8, 2025 16:43
@devversion devversion added action: merge The PR is ready for merge by the caretaker target: rc This PR is targeted for the next release-candidate labels Jan 14, 2025
@devversion devversion merged commit f9a9db6 into angular:main Jan 14, 2025
28 checks passed
devversion pushed a commit that referenced this pull request Jan 14, 2025
* refactor: move material.aio GHA to the root

This makes them functional again. To keep this change simple, we just update the working directory but run the same things

* refactor: upload testlogs when test step fails

* refactor: pin chromium test to same Ubuntu as before

See last passing job in old repo: https://github.com/angular/material.angular.io/actions/runs/12390917032/job/34586949768

* refactor: only trigger material.aio workflows when files touched in that folder

(cherry picked from commit f9a9db6)
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Feb 14, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker target: rc This PR is targeted for the next release-candidate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants