Skip to content

fix: replace blocked preview sticky comment action#3113

Merged
gtrivedi88 merged 1 commit into
mainfrom
fix/preview-sticky-comment-action
May 28, 2026
Merged

fix: replace blocked preview sticky comment action#3113
gtrivedi88 merged 1 commit into
mainfrom
fix/preview-sticky-comment-action

Conversation

@gtrivedi88

Copy link
Copy Markdown
Contributor

Summary

  • The actions-cool/maintain-one-comment@v3 repository was blocked by GitHub for a TOS violation on 2026-05-19
  • All "Preview sticky comment" workflow runs have failed since that date with Repository access blocked
  • Replaced with marocchino/sticky-pull-request-comment@v2, which provides the same sticky comment functionality

Evidence

  • Last successful run: 2026-05-18 (jtbd-install-category branch)
  • First failure: 2026-05-19 (docs-che-operator-2117-automated-prometheus branch)
  • GitHub API confirms: {"reason": "tos", "created_at": "2026-05-19T00:34:15Z"}

Test plan

  • Verify the "Preview sticky comment" check passes on this PR
  • Verify a sticky comment is posted on the PR

Fixes: CRW-11078

🤖 Generated with Claude Code

The `actions-cool/maintain-one-comment@v3` repository was blocked by
GitHub for a Terms of Service violation on 2026-05-19, causing all
"Preview sticky comment" workflow runs to fail.

Replace with `marocchino/sticky-pull-request-comment@v2`, which
provides the same sticky comment functionality.

Fixes: CRW-11078

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@gtrivedi88 gtrivedi88 requested review from a team, deerskindoll and mkuznyetsov as code owners May 28, 2026 16:11
@gtrivedi88 gtrivedi88 requested a review from amisevsk May 28, 2026 16:11
@github-actions

github-actions Bot commented May 28, 2026

Copy link
Copy Markdown

Click here to review and test in web IDE: Contribute

@gtrivedi88

Copy link
Copy Markdown
Contributor Author

Note: The "Preview sticky comment" check is still failing on this PR because the workflow uses pull_request_target, which always runs the workflow file from the base branch (main), not the PR branch. So the old blocked action is still being used.

This is a chicken-and-egg problem — the fix can only take effect after it's merged into main. The change itself is a straightforward 1:1 replacement of the blocked action.

@svor svor left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@gtrivedi88 gtrivedi88 merged commit 6b43300 into main May 28, 2026
11 of 12 checks passed
@gtrivedi88 gtrivedi88 deleted the fix/preview-sticky-comment-action branch May 28, 2026 16:28
svor pushed a commit that referenced this pull request May 29, 2026
The `actions-cool/maintain-one-comment@v3` repository was blocked by
GitHub for a TOS violation on 2026-05-19. This is the same issue fixed
in #3113 for preview-sticky-comment.yml — the publish-netlify workflow
also uses this action for the "Update status comment" step.

Replace with `marocchino/sticky-pull-request-comment@v2`.

Related: CRW-11078

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
ibuziuk pushed a commit that referenced this pull request Jun 16, 2026
* docs: add AI provider configuration and usage docs

Assisted-by: Claude Sonnet 4.6
Signed-off-by: Oleksii Orel <oorel@redhat.com>

* docs: fix broken cross-references and section levels in AI docs

- Fix section title levels in configuring-an-ai-provider-api-key.adoc
  (=== to == to follow expected sequence after = heading)
- Add end-user-guide: module prefix to cross-module xrefs in
  ai-provider-api-key-secret-reference.adoc and configuring-ai-providers.adoc
- Remove non-existent aiProviders and defaultAiProvider xrefs from
  checluster-custom-resource-fields-reference.adoc (AI config is
  ConfigMap-based, not CheCluster CR fields)

Assisted-by: Claude Sonnet 4.6
Signed-off-by: Oleksii Orel <oorel@redhat.com>

* docs: address PR review feedback for AI docs

- Sentence-case all :navtitle: values
- Add [role="_abstract"] to all 5 modules with JTBD-focused text
- Use imperative verb in procedure titles (Configure, not Configuring)
- Use noun phrase for concept title (AI assistants in workspaces)
- Fix :description: fields to explain what/why, not restate the title
- Add Tech-Preview note to configuring-ai-providers.adoc
- Consolidate two consecutive NOTE admonitions into one
- Remove custom subheadings from procedure module; present both
  paths as a single numbered list with choice items
- Fix hardcoded Gemini verification commands to generic placeholders
- Fix callout 4: correct regex description (all non-identifier chars,
  not just slashes, are replaced with dashes)
- Fix additional resources link: DevWorkspace Operator -> Devfile docs
- Extract changing-the-ai-tool procedure into its own module and add
  xref from the concept page
- Add changing-the-ai-tool-on-a-workspace.adoc to end-user nav

Assisted-by: Claude Sonnet 4.6
Signed-off-by: Oleksii Orel <oorel@redhat.com>

* fix: use correct Antora family prefix for Tech-Preview snippet include

Replace examples/ path with example$ family prefix required by Antora
for including files from the examples/ directory.

Assisted-by: Claude Sonnet 4.6
Signed-off-by: Oleksii Orel <oorel@redhat.com>

* docs: use OPENAI_API_KEY and opencodeai/opencode as the canonical example

Replace all GEMINI_API_KEY and ANTHROPIC_API_KEY references with
OPENAI_API_KEY. Replace google/gemini and anthropic/claude provider IDs
with opencodeai/opencode. Simplify the url-parameter page to a single
provider example.

Assisted-by: Claude Sonnet 4.6
Signed-off-by: Oleksii Orel <oorel@redhat.com>

* docs: add OpenCode injector image Dockerfile and registry.json guide

- Replace Gemini/Claude dual-provider example with a single OpenCode
  provider using OPENAI_API_KEY
- Add Procedure step with a minimal Dockerfile for building a custom
  injector image, based on che-incubator/che-ai-tool-images/dockerfiles/
  opencode/Dockerfile; explains multi-stage build, wrapper script for
  OpenShift arbitrary UIDs, and multi-arch build command
- Reference che-incubator/che-ai-tool-images for maintained examples
- Document all registry.json fields with numbered callouts

Assisted-by: Claude Sonnet 4.6
Signed-off-by: Oleksii Orel <oorel@redhat.com>

* chore: retrigger CI after preview action fix (#3113)

---------

Signed-off-by: Oleksii Orel <oorel@redhat.com>
Co-authored-by: Gaurav Trivedi <gtrivedi@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants