Skip to content

Conversation

Artur-
Copy link
Member

@Artur- Artur- commented Oct 7, 2025

No description provided.

@Artur- Artur- force-pushed the flow-spotless-update branch from d13ef9c to 58cd01c Compare October 7, 2025 13:03
@Artur- Artur- force-pushed the flow-spotless-update branch from 58cd01c to 52aec19 Compare October 7, 2025 13:06
@vaadin vaadin deleted a comment from github-actions bot Oct 7, 2025
@Artur- Artur- force-pushed the Artur--patch-16 branch 2 times, most recently from 06161db to 38db162 Compare October 7, 2025 13:38
@vaadin vaadin deleted a comment from github-actions bot Oct 7, 2025
Artur- and others added 4 commits October 8, 2025 09:44
- Modified formatter workflow to automatically commit and push formatting changes
- Added infinite loop detection by checking if last commit author was github-actions bot
- Changed permissions to allow contents: write for pushing commits
- Updated validation workflow to run after formatter completes
- Added conditional execution to skip validation if formatter committed changes
- Formatter will retrigger after auto-commit to verify formatting is correct

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
- Merged formatter.yml into validation.yml as a single workflow
- Formatter runs first on pull_request_target events
- If formatting changes are committed, workflow stops and retriggers
- On second run, detects bot commit and skips formatting, proceeds to tests
- Build and test jobs only run if formatter succeeds or is skipped
- Prevents infinite loops by detecting bot commits and not formatting again

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
- Removed workflow stop after formatter commits changes
- Pass new commit SHA to all downstream jobs (build, unit-tests, it-tests, test-results)
- All jobs now checkout the formatted code using new_sha output from formatter
- Validation runs in same workflow after formatting, no separate trigger needed
- Fallback to original HEAD_SHA when formatter is skipped (push to main branches)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
- Require VAADIN_BOT_TOKEN secret for formatter workflow
- Use PAT instead of GITHUB_TOKEN to push commits (enables workflow triggers)
- Fail build if token is not configured
- Stop workflow after formatter commits (new workflow will be triggered)
- On second run, formatter detects bot commit and skips, validation proceeds
- Revert new_sha passing logic (not needed with PAT approach)

To set up:
1. Create GitHub PAT with repo and workflow permissions
2. Add as repository secret named VAADIN_BOT_TOKEN

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
@Artur- Artur- force-pushed the flow-spotless-update branch from b217255 to 347f208 Compare October 8, 2025 06:44
@Artur- Artur- force-pushed the Artur--patch-16 branch 2 times, most recently from f429432 to 77ff649 Compare October 8, 2025 08:57
@Artur- Artur- force-pushed the flow-spotless-update branch from a1b95ee to 347f208 Compare October 8, 2025 09:32
@Artur- Artur- force-pushed the flow-spotless-update branch from ff69418 to 37e8c75 Compare October 8, 2025 09:38
Copy link

sonarqubecloud bot commented Oct 8, 2025

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants