Skip to content
This repository has been archived by the owner on Dec 26, 2024. It is now read-only.

ci(workflows): disable Fly.io deployment workflows in preparation for migration to Vercel #136

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

mauvehed
Copy link
Owner

@mauvehed mauvehed commented Dec 19, 2024

The Fly.io deployment workflows for both production and pull requests are disabled. This change is made to facilitate the migration of the deployment process to Vercel. By commenting out the relevant sections, the workflows are effectively paused without being deleted, allowing for potential reactivation if needed.

Summary by Sourcery

CI:

  • Disable Fly.io deployment workflows for production and pull requests.

… migration to Vercel

The Fly.io deployment workflows for both production and pull requests are disabled. This change is made to facilitate the migration of the deployment process to Vercel. By commenting out the relevant sections, the workflows are effectively paused without being deleted, allowing for potential reactivation if needed.
Copy link
Contributor

sourcery-ai bot commented Dec 19, 2024

Reviewer's Guide by Sourcery

This pull request disables the Fly.io deployment workflows for both production and pull requests in preparation for a migration to Vercel. The workflows are disabled by commenting out the trigger sections, effectively pausing them without deletion.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
Disabled the production deployment workflow triggers.
  • Commented out the lines that trigger the workflow on release events.
  • Commented out the lines that trigger the workflow on pull request close events.
.github/workflows/deploy-flyio-app.yml
Disabled the pull request deployment workflow triggers.
  • Commented out the lines that trigger the workflow on pull request close events.
.github/workflows/deploy-flyio-pr.yml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time. You can also use
    this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@mauvehed mauvehed enabled auto-merge (squash) December 19, 2024 23:18
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant