:bug: Broken link in /docs/resources.md: https://ibm.biz/rossoctl-slack
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 74/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- documentation
Research direction
Open docs/resources.md and inspect the entry for https://ibm.biz/rossoctl-slack. Find a valid destination for the project’s Slack resource and update the broken link. Verify that the replacement resolves and that the resource entry still points to the intended community.
Written by the indexing model from the issue text.
Description
Describe the bug
Broken link detected by automated link health scan.
Repo: rossoctl/rossoctl
File: /docs/resources.md
Broken URL: https://ibm.biz/rossoctl-slack
HTTP Status: error
First detected: 2026-11-11
Scan ID: 2026-11-11-001
Steps To Reproduce
- Open https://github.com/rossoctl/rossoctl/blob/main//docs/resources.md
- Click or follow the link to
https://ibm.biz/rossoctl-slack - Observe error error
Expected Behavior
The link should resolve to valid documentation.
Additional Context
Category: external
Detected by RepoMan Link Health Scanner (cron: link-health-scanner)
- Dominant language
- Python
- Stars
- 304
- Forks
- 109
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 rossoctl/rossoctl
-
:bug: Broken link in /terraform/management-cluster/README.md: https://hypershift-docs.netlify.app/Open
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
Maintainers usually reply within 1 day
All issues in rossoctl/rossoctl
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
UKGovernmentBEIS/inspect_ai#6512 ·
Maintainers usually reply within 1 day
-
area/c++ area/core kind/bug-report
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tensorflow/quantum#1140 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
Kav-K/GPTDiscord#501 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
UKGovernmentBEIS/inspect_evals#2863 · 1 comment ·
Maintainers usually reply within 1 day