We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
refer to Certseeds/openpgpage#4 use actions to trigger code-review
name: Code Review permissions: contents: read pull-requests: write on: pull_request: types: [opened, reopened, synchronize] jobs: test: if: github.repository == 'Certseeds/openpgpage' runs-on: ubuntu-latest steps: - uses: anc95/ChatGPT-CodeReview@v1 env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} OPENAI_API_KEY: ${{ secrets.CHATGPT_SESSION_TOKEN }}
1st commit trigger a review, get a meaningful response. 2nd force-push trigger a review, find a meaingful response too. but the 3rd and 4th push can trigger actions but do not find response, is that corect? ps: the 3rd action https://github.com/Certseeds/openpgpage/actions/runs/4315833869 the 4th action https://github.com/Certseeds/openpgpage/actions/runs/4315849686
The text was updated successfully, but these errors were encountered:
ps: maybe update action's json file with newest code is helpful
Sorry, something went wrong.
@Certseeds Have you tried change the action to anc95/ChatGPT-CodeReview@main (the code on main branch) to see if it would work?
anc95/ChatGPT-CodeReview@main
yes, it works.
the bug come from commit bb605aa
No branches or pull requests
refer to Certseeds/openpgpage#4
use actions to trigger code-review
1st commit trigger a review, get a meaningful response.
2nd force-push trigger a review, find a meaingful response too.
but the 3rd and 4th push can trigger actions but do not find response, is that corect?
ps:
the 3rd action https://github.com/Certseeds/openpgpage/actions/runs/4315833869
the 4th action https://github.com/Certseeds/openpgpage/actions/runs/4315849686
The text was updated successfully, but these errors were encountered: