feat: add vercel deploy button

[rodrigopavezi]

Change:

• Add Vercel Deploy Button to README Add a "Deploy to Vercel" button on the README #36

Summary by CodeRabbit

• New Features

  • Enhanced deployment instructions for the Request Invoicing template.
  • Added a visual button for easy deployment with Vercel.
  • Included guidance on creating a .env or .env.local file with necessary environment variables.

• Documentation

  • Retained existing deployment information for EasyPanel, GitHub Actions, and Heroku Buildpacks.

[coderabbitai]

Walkthrough

The changes made to the project primarily focus on enhancing the deployment instructions within the README.md file for the Request Invoicing template. A new section has been introduced to provide explicit guidance on deploying the application using Vercel, including a visual button for deployment. Additionally, instructions regarding the creation of a .env or .env.local file and the necessary environment variables have been included. Existing deployment options using EasyPanel, GitHub Actions, and Heroku Buildpacks remain in the documentation.

Changes

File	Change Summary
README.md	Added deployment instructions for Vercel, a visual button for "Deploy with Vercel," and notes on creating a .env or .env.local file with required environment variables. Existing deployment options retained.

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between afa00ff and 3a1fc81.

Files selected for processing (1)

• README.md (2 hunks)

Additional comments not posted (2)

README.md (2)

36-38: LGTM!

The addition of the "Deploy with Vercel" section and the corresponding Markdown button is a great enhancement to the deployment instructions. The button is correctly formatted and links to the appropriate Vercel deployment page with relevant query parameters. This change aligns well with the PR objective of streamlining the deployment process for users.

---

38-38: Looks good!

The note about creating a .env or .env.local file with the required environment variables is a helpful addition to the deployment instructions. It provides clear guidance to users on the necessary steps before deploying the project and refers to the available environment variables and the .env.example file for reference. This information will help users set up the project correctly.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.