Skip to content

fix: ready-for-e2e label#16100

Merged
zomars merged 2 commits intomainfrom
fix-ready-for-e2e-not-triggering-e2e
Aug 14, 2024
Merged

fix: ready-for-e2e label#16100
zomars merged 2 commits intomainfrom
fix-ready-for-e2e-not-triggering-e2e

Conversation

@emrysal
Copy link
Copy Markdown
Contributor

@emrysal emrysal commented Aug 6, 2024

Attempt at fixing the ready-for-e2e label not triggering the PR Update workflow.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Aug 6, 2024

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "Update pr-review.yml". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

@graphite-app graphite-app Bot requested a review from a team August 6, 2024 18:26
@emrysal emrysal changed the title Update pr-review.yml fix: ready-for-e2e label Aug 6, 2024
@keithwillcode keithwillcode added core area: core, team members only foundation labels Aug 6, 2024
@dosubot dosubot Bot added the 🐛 bug Something isn't working label Aug 6, 2024
@vercel
Copy link
Copy Markdown

vercel Bot commented Aug 6, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
ai ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 14, 2024 1:45am
2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
cal ⬜️ Ignored (Inspect) Visit Preview Aug 14, 2024 1:45am
calcom-web-canary ⬜️ Ignored (Inspect) Visit Preview Aug 14, 2024 1:45am

@graphite-app
Copy link
Copy Markdown

graphite-app Bot commented Aug 6, 2024

Graphite Automations

"Add foundation team as reviewer" took an action on this PR • (08/06/24)

1 reviewer was added to this PR based on Keith Williams's automation.

Copy link
Copy Markdown
Contributor

@zomars zomars left a comment

Choose a reason for hiding this comment

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

How do we know this will fix it? What was causing trouble?

Copy link
Copy Markdown
Contributor

@zomars zomars left a comment

Choose a reason for hiding this comment

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

Ship it

@zomars zomars merged commit 050abd9 into main Aug 14, 2024
Copy link
Copy Markdown
Contributor

zomars commented Aug 14, 2024

Merge activity

@zomars zomars deleted the fix-ready-for-e2e-not-triggering-e2e branch August 14, 2024 18:24
@github-actions
Copy link
Copy Markdown
Contributor

E2E results are ready!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🐛 bug Something isn't working core area: core, team members only foundation ready-for-e2e

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants