Skip to content

Revert: Annuler les changements workflow CodeRabbit #25

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.

Sign up for GitHub

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
EthanThePhoenix38 merged 1 commit into from
Jan 15, 2026
Merged

Revert: Annuler les changements workflow CodeRabbit #25

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 0 additions & 27 deletions .github/coderabbit.yaml
View file
Open in desktop

This file was deleted.

14 changes: 4 additions & 10 deletions .github/workflows/update-ai-pulse.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,8 +10,6 @@ on:

permissions:
contents: write
pull-requests: write
issues: write

jobs:
aggregate-and-post:
Expand All @@ -20,9 +18,6 @@ jobs:
steps:
- name: Check out repository
uses: actions/checkout@v3
Copy link

Copilot AI Jan 15, 2026

Choose a reason for hiding this comment

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

Without explicitly providing a token to the checkout action or persisting credentials, the subsequent git push may fail with authentication errors. The default GITHUB_TOKEN provided to workflows may not be automatically available for git operations. Consider either adding 'token: ${{ secrets.GITHUB_TOKEN }}' to the checkout action or ensuring that authentication is properly configured for the git push operation.

Suggested change
uses: actions/checkout@v3
uses: actions/checkout@v3
with:
token: ${{ secrets.GITHUB_TOKEN }}

Copilot uses AI. Check for mistakes.
with:
token: ${{ secrets.GITHUB_TOKEN }}
persist-credentials: true

- name: Set up Node.js
uses: actions/setup-node@v4
Expand All @@ -48,16 +43,15 @@ jobs:
- name: Commit and push changes
env:
GIT_AUTHOR_EMAIL: ${{ secrets.GIT_AUTHOR_EMAIL }}
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: |
git config --global user.name 'github-actions[bot]'
git config --global user.email '41898282+github-actions[bot]@users.noreply.github.com'
git config --global user.name 'ThePhoenixAgency'
git config --global user.email "${GIT_AUTHOR_EMAIL}"
git add .

if ! git diff --cached --exit-code; then
UTC_DATE=$(date -u +'%a %b %d %H:%M:%S UTC %Y')
git commit -m "Updated AI-Pulse: $UTC_DATE [skip ci]"
git push origin main
git commit -m "Updated AI-Pulse: $UTC_DATE"
Copy link

Copilot AI Jan 15, 2026

Choose a reason for hiding this comment

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

The commit message no longer includes '[skip ci]' which was present in the reverted version. This means every automated commit will trigger the workflow again due to the 'on: push: branches: - main' trigger, potentially creating an infinite loop. Consider adding '[skip ci]' back to the commit message to prevent the workflow from triggering itself.

Suggested change
git commit -m "Updated AI-Pulse: $UTC_DATE"
git commit -m "Updated AI-Pulse: $UTC_DATE [skip ci]"

Copilot uses AI. Check for mistakes.
git push
Comment on lines 51 to +54
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot Jan 15, 2026

Choose a reason for hiding this comment

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

P1 Badge Restore CI skip to prevent recursive workflow runs

Because this workflow triggers on push to main, removing the [skip ci] marker from the commit message means the job’s own git push will immediately retrigger itself. src/aggregator.js always rewrites the README with a fresh Last Update timestamp, so every run creates a new commit and the cycle repeats, potentially creating an endless cascade of runs and commits. This only happens when the workflow is triggered by a push (including the push it makes itself), but that is the default here.

Useful? React with 👍 / 👎.

Copy link

Copilot AI Jan 15, 2026

Choose a reason for hiding this comment

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

The git push command without explicit branch specification may fail or push to an unexpected branch. When the workflow runs on a schedule or via workflow_dispatch, it may be in a detached HEAD state. Consider explicitly specifying the branch and remote as 'git push origin main' to ensure the changes are pushed to the correct branch consistently.

Suggested change
git push
git push origin main

Copilot uses AI. Check for mistakes.
else
echo "No changes to commit"
fi