Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Additional data in the GitHub connector

Answered
Ana Cañizares García User

Hi,

are there any plans to extend the GitHub's connector schema in the near future?

We would be very interested in getting data for the following events:

* auto_merge_enabled

* auto_merge_disabled

* added_to_merge_queue

* removed_from_merge_queue

These are available via the GitHub's HTTP API: https://docs.github.com/en/rest/issues/timeline?apiVersion=2022-11-28#list-timeline-events-for-an-issue

Thank you.

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Official comment
    Alison Fivetranner

    Hi Ana,

    Thank you for making this feature request for enhancing the GitHub connector schema with additional merge queue events, its a great suggestion and has been added to our feature improvements backlog.

    To help us better understand how to add these events in the most helpful way, could you share more details about how you plan to use these events?

    I'm also curious if you'd expect the table that we create to hold these events to be an append only table - where you would have to look for the latest entry to know the current state of a ticket or some other schema?

    We will keep this thread updated with any developments regarding this feature.

    Thanks,
    Alison

  • Ana Cañizares García User
    • Edited

    Hi Alison,

    I'm glad that you consider implementing this! Could you please give me a rough estimate for the implementation time? That would help me decide if it makes sense for us to wait for your implementation or build something ourselves.

    The schema I was experimenting with has these 2 tables:
    *automerge_pull_request*
    id,
    enabled_at: datetime,
    disabled_at: datetime | null,
    enabled_by: user_id,
    disabled_by: user_id | null
    pull_request_id: integer

    *merge_queue_attempts*
    id,
    added_to_merge_queue_at: datetime
    removed_from_merge_queue_at: datetime | null
    removal_actor_type: 'User' | 'Bot' | null
    pull_request_id: integer

    There might be better options, but this has worked well for my current use case.