Skip to content

Solved! Build error on expo 54 / react native 0.81 (working build demonstrator script linked in comments now) #4996

Solved! Build error on expo 54 / react native 0.81 (working build demonstrator script linked in comments now)

Solved! Build error on expo 54 / react native 0.81 (working build demonstrator script linked in comments now) #4996

Workflow file for this run

name: Update labels on issues with OP response
on:
issue_comment:
types: [created]
jobs:
label-op-response:
runs-on: ubuntu-latest
steps:
- name: Check if the comment is from the OP
id: check-op
run: |
OP=${{ github.event.issue.user.login }}
COMMENTER=${{ github.event.comment.user.login }}
if [ "$OP" = "$COMMENTER" ]; then
echo "op_comment=true" >> $GITHUB_ENV
else
echo "op_comment=false" >> $GITHUB_ENV
fi
- name: Add 'Needs Attention' label if OP responded and it was open
if: env.op_comment == 'true' && github.event.issue.state == 'open'
# https://github.com/actions-ecosystem/action-add-labels/releases
uses: actions-ecosystem/action-add-labels@18f1af5e3544586314bbe15c0273249c770b2daf # v1
with:
labels: 'Needs Attention'
env:
GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
- name: Remove 'blocked customer-response' label if OP responded and it was open
if: env.op_comment == 'true' && github.event.issue.state == 'open'
# https://github.com/actions-ecosystem/action-remove-labels/releases
uses: actions-ecosystem/action-remove-labels@2ce5d41b4b6aa8503e285553f75ed56e0a40bae0 # v1
with:
labels: 'blocked: customer-response'
env:
GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
- name: Add comment if OP responded but issue was closed
if: env.op_comment == 'true' && github.event.issue.state == 'closed'
# https://github.com/actions-ecosystem/action-create-comment/releases
uses: actions-ecosystem/action-create-comment@e23bc59fbff7aac7f9044bd66c2dc0fe1286f80b # v1
with:
github_token: ${{ secrets.GH_TOKEN }}
body: |
In order to prioritize work in this repository, closed issues and pull requests do not regularly receive attention.
If the underlying issue or pull request still requires attention, opening a new issue with a reproduction
after testing with current versions, or reposting the pull request as a new PR may be the most effective way forward.