Get Github branch name on new push/commit

Feature Requests
1

I’ve looked through New Commit (Instant) and New Push events and they got what I mainly need but I would like to get the commiter’s branch name that they commited to which doesn’t seem to be a option on those trigger events. I tried to get Updated Repository (Instant) to listen for commit events but that wouldn’t work for some reason.

Would be a great little feature for what I’m working with.

Cheers.

2

Hi @ReaLadge

I’ve looked through New Commit (Instant) and New Push events and they got what I mainly need but I would like to get the commiter’s branch name that they commited to which doesn’t seem to be a option on those trigger events.

Have you tried using another Github action or Github API request to enrich your workflow with this data?

I tried to get Updated Repository (Instant) to listen for commit events but that wouldn’t work for some reason.

Can you describe which portion of the trigger wasn’t working properly for you? Better yet, could you describe the issue in a bug card? A Pipedream developer or community developer can help you!

3

I’ve tried a few other Github actions including the API one. I did find “Default Branch” and “Master Branch” output sections in the Event > Repository > Owner with the “New Push” Github action but they don’t update latest branch edited. If you have other information about how to obtaining the latest edited branch, any help would be appreciated.

Just in general it’s not listening to requests when I add the Updated Repository (Instant) action try to generate events from GitHub. Just sits there waiting for events. I’ve done pushes and made new branches and nothing gets picked up.

4

Ok I found it. Don’t know how I missed it but it’s under “Event > ref” in New Push action. My bad must of got confused on my naming conventions haha. I don’t know how to delete this post so imma leave this here.

1 Like
5

Hi @ReaLadge I’m glad you were able to find that! Leaving posts with answers is helpful to others looking for the same answer in the future anyway :slight_smile:

We have a Github issue open from your other report on the non-loading options:

Please feel free to comment and react to it so you received real time updates when it’s fixed!