Skip to content

Implemented Operations between two TensorDicts are defined by their position in their respective trees, not their keys #334

Implemented Operations between two TensorDicts are defined by their position in their respective trees, not their keys

Implemented Operations between two TensorDicts are defined by their position in their respective trees, not their keys #334

Workflow file for this run

# Allow users to automatically tag themselves to issues
#
# Usage:
# - a github user (a member of the repo) needs to comment
# with "#self-assign" on an issue to be assigned to them.
#------------------------------------------------------------
name: Self-assign
on:
issue_comment:
types: created
concurrency:
# Documentation suggests ${{ github.head_ref }}, but that's only available on pull_request/pull_request_target triggers, so using ${{ github.ref }}.
# On master, we want all builds to complete even if merging happens faster to make it easier to discover at which point something broke.
group: ${{ github.workflow }}-${{ github.ref == 'refs/heads/main' && format('ci-master-{0}', github.sha) || format('ci-{0}', github.ref) }}
cancel-in-progress: true
jobs:
one:
runs-on: ubuntu-latest
if: >-
(github.event.comment.body == '#take' ||
github.event.comment.body == '#self-assign')
steps:
- run: |
echo "Assigning issue ${{ github.event.issue.number }} to ${{ github.event.comment.user.login }}"
curl -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \
-d '{"assignees": ["${{ github.event.comment.user.login }}"]}' \
https://api.github.com/repos/${{ github.repository }}/issues/${{ github.event.issue.number }}/assignees
echo "Done 🔥 "