home / github / issues

Menu
  • GraphQL API
  • Search all tables

issues: 778487167

This data as json

id node_id number title user state locked assignee milestone comments created_at updated_at closed_at author_association active_lock_reason draft pull_request body reactions performed_via_github_app state_reason repo type
778487167 MDExOlB1bGxSZXF1ZXN0NTQ4NTY2MDMx 4764 action to detect a keyword in the commit summary line 14808389 closed 0     2 2021-01-05T01:03:56Z 2021-01-05T20:39:15Z 2021-01-05T20:39:12Z MEMBER   0 pydata/xarray/pulls/4764

follow-up to #4729 and #4730

To use the detect-ci-trigger action in workflows, add a new job: yaml detect-ci-trigger: name: Detect CI Trigger runs-on: ubuntu-latest outputs: triggered: ${{ steps.detect-trigger.outputs.trigger-found }} steps: - uses: actions/checkout@v2 - uses: ./.github/actions/detect-ci-trigger id: detect-trigger with: keyword: "<keyword>" then require the new job in jobs that should be conditionally skipped: yaml my-ci-job: runs-on: ubuntu-latest needs: detect-ci-trigger if: needs.detect-ci-trigger.outputs.triggered == 'false' # for skip-ci # if: needs.detect-ci-trigger.outputs.triggered == 'true' # for test-upstream steps: - actions/checkout@v2 # ...

~unfortunately, this still requires actions/checkout with fetch-depth, I can't seem to get a git fetch in the action script to work.~ Edit: git fetch --deepen=1 instead of git fetch --depth=2 seems to work.

cc @andersy005

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/4764/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
    13221727 pull

Links from other tables

  • 1 row from issues_id in issues_labels
  • 2 rows from issue in issue_comments
Powered by Datasette · Queries took 0.766ms · About: xarray-datasette