Skip to content

manually publish#71

Merged
ValwareIRC merged 1 commit into
mainfrom
manually-publish
Oct 2, 2025
Merged

manually publish#71
ValwareIRC merged 1 commit into
mainfrom
manually-publish

Conversation

@matheusfillipe
Copy link
Copy Markdown
Contributor

@matheusfillipe matheusfillipe commented Oct 2, 2025

Summary by CodeRabbit

  • Chores
    • Enabled manual triggering of the publish workflow from GitHub Actions, allowing on-demand runs (e.g., for hotfixes or urgent releases) without waiting for automatic triggers.
    • Updated workflow conditions so version information is properly collected during manual runs, ensuring consistent release metadata.
    • Improves operational control and flexibility for release management with no impact on application behavior or user experience.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Oct 2, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

Adds a manual trigger to the GitHub Actions publish workflow and updates the job condition so the version collection runs when manually dispatched.

Changes

Cohort / File(s) Summary of changes
CI Workflow triggers and conditions
.github/workflows/publish.yaml
Added workflow_dispatch to triggers; updated collect-version job condition to include workflow_dispatch event.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  participant Dev as Developer
  participant GH as GitHub Actions
  participant WF as publish.yaml
  participant Job as collect-version

  rect rgb(235, 245, 255)
    note over Dev,GH: New/updated control flow
    Dev->>GH: Push/Tag (existing) OR Manual dispatch (workflow_dispatch)
    GH->>WF: Trigger workflow
    alt Event is push/tag or workflow_dispatch
      WF->>Job: Evaluate condition (includes workflow_dispatch)
      Job-->>WF: Runs collect-version
    else Other events
      WF-->>Job: Skipped
    end
  end
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I tap my paw—dispatch on cue,
A workflow wakes to something new.
Version crumbs collected neat,
YAML paths beneath my feet.
With a hop, the publish sings—
Manual magic flaps its wings.

✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch manually-publish

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6bd8499 and b80b44e.

📒 Files selected for processing (1)
  • .github/workflows/publish.yaml (1 hunks)

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Oct 2, 2025

Pages Preview
Preview URL: https://manually-publish.obsidianirc.pages.dev

Automated deployment preview for the PR in the Cloudflare Pages.

@ValwareIRC
Copy link
Copy Markdown
Contributor

manually publish what

@matheusfillipe
Copy link
Copy Markdown
Contributor Author

manually publish what

Github workflows can be manually triggered. This will hopefully allow you or me to manually trigger this workflow for a test build in any branch, instead of waiting for main branch. I don't want this to be automatically in every push as they take very long each time.

@matheusfillipe
Copy link
Copy Markdown
Contributor Author

matheusfillipe commented Oct 2, 2025

manually publish what

Github workflows can be manually triggered. This will hopefully allow you or me to manually trigger this workflow for a test build in any branch, instead of waiting for main branch. I don't want this to be automatically in every push as they take very long each time.

@matheusfillipe matheusfillipe reopened this Oct 2, 2025
@ValwareIRC ValwareIRC merged commit d8d8dda into main Oct 2, 2025
5 checks passed
@matheusfillipe matheusfillipe deleted the manually-publish branch October 2, 2025 17:20
zocram4cc pushed a commit to zocram4cc/ObsidianIRC that referenced this pull request Feb 17, 2026
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