Thank you for this work!

--------
Regards,

Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.

"Do not go where the path may lead,
 go instead where there is no path and leave a trail."


On Sat, Mar 21, 2020 at 3:49 PM Daniel Alley <dal...@redhat.com> wrote:

> This is great!   Awesome work, David <3
>
> On Sat, Mar 21, 2020 at 10:38 AM David Davis <davidda...@redhat.com>
> wrote:
>
>> I created a PR workflow in Github Actions so I could learn more about
>> Github Actions.
>>
>> Here's the issue and my PR against plugin_template:
>>
>> https://pulp.plan.io/issues/4365
>> https://github.com/pulp/plugin_template/pull/199
>>
>> The PR processor will listen for new PRs in Github and when it detects a
>> newly opened PR it does two things:
>>
>> - Updates the pulp.plan.io issue
>>   - Adds a comment with a link to the Github PR (regardless of the
>> issue's status)
>>   - Sets the issue status to POST if it's in NEW or ASSIGNED
>> - Adds labels to the Github PR
>>   - Right now, this is only "Needs Cherry Pick" which is added if tracker
>> == "Issue"
>>
>> I have an example that demonstrates the PR processor. Here's a story and
>> its PR:
>>
>> https://pulp.plan.io/issues/6381
>> https://github.com/daviddavis/pulp_file/pull/11
>>
>> The PR processor will also comment with a warning if there is no issue
>> attached:
>>
>> https://github.com/daviddavis/pulp_file/pull/12
>>
>> Questions and feedback welcome.
>>
>> David
>> _______________________________________________
>> Pulp-dev mailing list
>> Pulp-dev@redhat.com
>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>
> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
_______________________________________________
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Reply via email to