chore: initialize fullsend per-repo installation#993
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
4ecf9c1 to
f27ffa3
Compare
|
Build succeeded. ✔️ pre-commit SUCCESS in 3m 24s |
lbarcziova
left a comment
lbarcziova
left a comment
There was a problem hiding this comment.
few comments, but I'm fine with testing this out
| secrets: | ||
| FULLSEND_GCP_WIF_PROVIDER: ${{ secrets.FULLSEND_GCP_WIF_PROVIDER }} | ||
| FULLSEND_GCP_PROJECT_ID: ${{ secrets.FULLSEND_GCP_PROJECT_ID }} | ||
| OTEL_EXPORTER_OTLP_TRACES_HEADERS: ${{ secrets.OTEL_EXPORTER_OTLP_TRACES_HEADERS }} |
There was a problem hiding this comment.
I don't see this set in repo, is it mandatory?
There was a problem hiding this comment.
yes, that's a good point, I'm gonna drop it; it was a default configuration
| permissions: | ||
| actions: write | ||
| id-token: write | ||
| contents: write | ||
| issues: write | ||
| packages: read | ||
| pull-requests: write |
| stop-fix: | ||
| if: >- | ||
| github.event_name == 'issue_comment' | ||
| && github.event.issue.pull_request | ||
| && github.event.comment.user.type != 'Bot' | ||
| && github.event.comment.body == '/fs-fix-stop' | ||
| && ( | ||
| github.event.comment.author_association == 'OWNER' | ||
| || github.event.comment.author_association == 'MEMBER' | ||
| || github.event.comment.author_association == 'COLLABORATOR' | ||
| || github.event.comment.author_association == 'CONTRIBUTOR' | ||
| || github.event.comment.user.login == github.event.issue.user.login | ||
| ) | ||
| runs-on: ubuntu-24.04 | ||
| permissions: | ||
| contents: read | ||
| issues: write | ||
| pull-requests: write | ||
| steps: | ||
| - name: Add fullsend-no-fix label and notify | ||
| env: | ||
| GH_TOKEN: ${{ github.token }} | ||
| PR_NUMBER: ${{ github.event.issue.number }} | ||
| REPO: ${{ github.repository }} | ||
| run: | | ||
| set -euo pipefail | ||
| gh label create "fullsend-no-fix" --repo "$REPO" \ | ||
| --description "Skip bot-triggered fix agent runs" --color "FBCA04" \ | ||
| --force 2>/dev/null || true | ||
| gh pr edit "$PR_NUMBER" --repo "$REPO" \ | ||
| --add-label "fullsend-no-fix" | ||
| gh pr comment "$PR_NUMBER" --repo "$REPO" \ | ||
| --body "Fix agent disabled for this PR. Remove the \`fullsend-no-fix\` label or use \`/fs-fix\` to re-engage." |
There was a problem hiding this comment.
does this essentially just label the issue? (in which case, do we really need it?)
There was a problem hiding this comment.
it is actually weird that only fix-stop workflow is here, and not the actual review, triage, code workflows
f27ffa3 to
4b119bc
Compare
|
Build succeeded. ✔️ pre-commit SUCCESS in 3m 25s |
3 participants
This PR adds the fullsend scaffold files for per-repo installation.
Merge this PR to activate fullsend workflows.
Edit: this PR was created with fullsend's CLI, hence the content, title and description