Repo

Why is the Repo Name Update Disabled?

We have intentionally disabled the ability to update the repository name after integration. This decision is based on how triggers are set up and how they interact with the webhook system for content generation.

Understanding the Issue

When you integrate a repository, RepoVox automatically sets up triggers in the database. These triggers listen for incoming webhook events to generate content. If you change the repository name:

1. The existing triggers in the database would become invalid because they are tied to the original repository.
2. If any content is currently being generated based on these triggers, it could cause disruptions in the database.
3. This could lead to data inconsistency and unexpected failures in content automation.

Recommended Solution

Instead of updating the repository name, customers should disconnect the entire integration and set it up as a new connection.

Steps to Disconnect and Reconnect:

1. Disconnect the current integration – This will remove all associated triggers from the database.
2. Reintegrate with the new repository name – This ensures a clean setup with fresh triggers.

By following this approach, you maintain a stable and error-free content automation experience. If you encounter any issues, feel free to reach out to support!

What is this use of scheduled field value?

RepoVox provides a scheduled posting feature that ensures content is delivered at the right time while efficiently handling webhook events from integrated platforms like GitHub.

How It Works

1. Webhook Event Handling

   • RepoVox listens to incoming webhook events from GitHub and other integrated platforms.
   • When an event (e.g., a pull request merge or commit) occurs, RepoVox processes the event and generates content based on predefined templates and AI analysis.

2. Deferred Content Publishing

   • Instead of immediately posting the generated content to connected platforms (Twitter, LinkedIn, etc.), RepoVox checks if scheduled posting is enabled for the user.
   • If scheduled posting is enabled, the content is stored but not published immediately.

3. Content Batching & Scheduled Execution

   • At the scheduled time (set by the user), RepoVox retrieves all pending generated content that was collected since the last scheduled execution.
   • The system then collates these posts into a batch and publishes them in bulk to the connected platforms.

Benefits of Scheduled Posting

• Avoids excessive posting: Prevents flooding social media with multiple updates at irregular intervals.
• Ensures consistency: Posts are delivered at a fixed time, optimizing engagement.
• Better control: Users can review, modify, or reorder scheduled content before it goes live.

Example Workflow

1. Webhook Event: A developer merges a pull request.
2. Content Generation: RepoVox generates a summary of the changes.
3. Storage: The content is stored in the pending queue (not published immediately).
4. Scheduled Execution: At 10 AM (user-defined time), all pending posts from the last 24 hours are published as a batch.

This ensures that RepoVox delivers content in an organized, efficient, and impactful manner. 🚀