mehrancodes/laravel-harbor

comment on PR after provision

Closed this issue · 1 comments

mehrancodes commented

Certainly! Here's an example of how you could structure the content for a GitHub issue comment using Markdown, which would be generated by Veyoze CLI tool. This comment format provides clear and concise information about the preview environment for a pull request:

# PR Preview Environment Details

Hello! Here are the details of the preview environment for this pull request:

| Service     | Location                                                    |
|-------------|-------------------------------------------------------------|
| **Website** | [GENERATED_DOMAIN.com](https://GENERATED_DOMAIN.com)        |
| **Database**| DATABASE_NAME                                               |

You can access the website by clicking on the link above. The database details are provided for backend access and testing purposes. If you encounter any issues or have further questions, please don't hesitate to reach out!

---
*This comment was automatically generated by Veyoze.*

This comment format includes:

  1. A title ("PR Preview Environment Details") for easy identification.
  2. An introductory message that briefly explains what the comment contains.
  3. A table with two columns, "Service" and "Location," detailing the website URL and database name.
  4. Instructions or additional information relevant to the user.
  5. A footer note indicating that this is an automated message generated by Veyoze tool.

Requirements

We need to take a github token (and PR/issue number possibly) while running the veyoze provision so we can comment on the related Pull Request after the provision is done.

mehrancodes commented

@shvansheikha thanks man! 🥳🚀 the PR got merged!