Reconcile enterprise/cloud doc divergence + add bump-last-updated tooling#1547
Reconcile enterprise/cloud doc divergence + add bump-last-updated tooling#1547justinegeffen wants to merge 22 commits into
Conversation
…ling Fixes drift bugs surfaced by the enterprise vs cloud audit, normalizes frontmatter date format across both trees, and adds a pre-commit hook + CI auto-trigger so last updated dates stay current. Full per-file rationale in enterprise-cloud-divergence-audit.md. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
❌ Deploy Preview for seqera-docs failed. Why did it fail? →
|
There was a problem hiding this comment.
Most of this PR is cosmetic and date added and changed improvements. So it looks worse than it actually is.
95% of these changes are not offensive.
I've been through the changes and flagged anything that I think needs checked. IMO - everything else can be skimmed.
The report at the end flags some important differences and can be reviewed separately for quick wins.
| ### Bitbucket | ||
|
|
||
| To connect to a private BitBucket repository, see the [BitBucket documentation](https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/) to learn how to create a BitBucket App password. Then, create a new credential in Seqera with these steps: | ||
| To connect to a private BitBucket repository, see [API tokens](https://support.atlassian.com/bitbucket-cloud/docs/api-tokens/) to learn how to create a BitBucket API token (the API token must have at least `read:repository:bitbucket` scope). Then, create a new credential in Seqera with these steps: |
There was a problem hiding this comment.
Check - is BitBucket fully services in Enterprise?
There was a problem hiding this comment.
@swampie, is this content still accurate?
Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Per PR review (christopher-hakkaart): pre-commit hook now fails explicitly with the exact fix command, matching the existing check-doc-tags pattern. CI workflow still auto-bumps on PR via a dedicated step so fork contributors and skipped local hooks merge with current dates. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
|
I'll check the scripts again next week. But otherwise looking good. |
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
| @@ -1,15 +1,26 @@ | |||
| name: Run pre-commit when requested via comment | |||
| name: Run pre-commit on PRs or via comment | |||
There was a problem hiding this comment.
I think we should add an author_association here to improve security.
Summary
date created: "YYYY-MM-DD"+last updated: "YYYY-MM-DD"bump-last-updatedpre-commit hook + extends pre-commit-fix.yaml to auto-trigger on PRs solast updated:stays current without manual effortThe full per-file rationale (decisions, ports, audit corrections, deliberately-untouched items) lives in enterprise-cloud-divergence-audit.md. That doc is the canonical decision log — it deliberately keeps this PR description short.
Test plan
bump-last-updatedhook works locally (pre-commit run bump-last-updated --all-files)pre-commit-fix.yamlworkflow runs on this PR'ssynchronizeevent and that the bot only commits a bump if dates are stalestudio:executeLaunch=❌,j21-26.04launcher row)🤖 Generated with Claude Code