Can comments be set to private if posted via this integration?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- github-actions
- Domain
- devops
Research direction
No file, test, or entry point is named. Start by tracing the integration's GitHub-comment synchronization path and checking how Teamwork accepts comment visibility or locking; done means comments posted by this integration are private or locked to internal users, if the integration supports that behavior.
Written by the indexing model from the issue text.
Description
We use teamwork internally and externally. We'd love for comments from this integration to be posted privately/locked to internal users if possible
- Dominant language
- Shell
- Stars
- 68
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Teamwork/github-sync
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Teamwork/github-sync#64 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Teamwork/github-sync#55 ·
All issues in Teamwork/github-sync
Similar issues
-
Update to NCCL 2.32 Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
conda-forge/nccl-feedstock#166 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
pop-os/plymouth-theme#43 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hykilpikonna/hyfetch#545 ·
-
on hold T: core-bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100