You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4312cad
Browse filesBrowse the repository at this point in the historyBrowse files
curl ran without --fail, so HTTP errors (a revoked token, a task the
token can't see, a Teamwork outage) were only logged and the run still
passed. A failed task lookup also carried on with "null" as the project
id. Network errors, on the other hand, aborted the run halfway, and a
hung API held the runner until the job timed out.
Pass --fail-with-body and --max-time 30, log what failed, carry on with
the other steps and tasks, then exit 1 if anything failed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ Create the next environment vars in your repository:
21
21
*`TEAMWORK_URI`: The URL of your installation (e.g.: https://yourcompany.teamwork.com)
22
22
*`TEAMWORK_API_TOKEN`: The API token to authenticate the workflow. Follow [this guide](https://support.teamwork.com/projects/using-teamwork/locating-your-api-key) to find your URL and API key.
23
23
24
-
**Please Note:** The Teamwork account associated with this API key is the account which these comments will be created under. If this user does not have permission to access the project, this action will be ignored.
24
+
**Please Note:** The Teamwork account associated with this API key is the account which these comments will be created under. If this user does not have permission to access a task's project, that task will be skipped and the workflow run will be marked as failed.
25
25
26
26
`GITHUB_TOKEN` doesn't need to be setup in the repository, this var is always available during the workflows execution.
27
27
@@ -59,7 +59,7 @@ jobs:
59
59
## Usage
60
60
When creating a new PR, write in the description of the PR the URL of the task. The action will automatically add a comment in the task. Optionally, you may choose for a lightweight comment that will only include the PR title, URL and the user that performed the action, to enable this option set the `LIGHTWEIGHT_COMMENT` input to `true`.
61
61
62
-
Please note, the comment will be created in Teamwork under the account you have attached to this action. If the API key of the user you are using does not have permissions to access certain projects, the comment will not be created.
62
+
Please note, the comment will be created in Teamwork under the account you have attached to this action. If the API key of the user you are using does not have permissions to access certain projects, the comment will not be created and the workflow run will report an error.
0 commit comments