Skip to content
This repository was archived by the owner on Sep 1, 2022. It is now read-only.
This repository was archived by the owner on Sep 1, 2022. It is now read-only.

Consider validating against PR titles instead of numbers #7

Open

Description

@hectorsector

When validating a learner's action, leaving everything up to the pull request number puts the learner in a state that they are unable to recover from. For example, after the learner merges say PR 2, and let's assume Learning Lab misses that event (it did in my testing), the learner is then unable to move forward because they are told to merge PR 2. Instead, we can capture the title, and tell the learner that all the need to do is merge a PR with that title.

- type: gate
every: true
gates:
- left: '{{ payload.pull_request.number }}'
operator: ===
right: '{{ store.firstPullNumber }}'
- left: '{{ payload.pull_request.merged }}'
else:
- type: respond
with: e-generic.md
data:
expected: merge pull request '{{ store.firstPullNumber }}'

Activity

  1. mattdavis0351 commented on Apr 18, 2020

    @mattdavis0351
    Contributor

    @hectorsector you ran into this issue even with the store implemented?

  2. hectorsector commented on Apr 22, 2020

    @hectorsector
    ContributorAuthor

    Yes! This is an issue with too strict of a validation on the PR number. The example I described above happened to me.

    I guess our options are:

    • do not validate against the PR number on a merge event
    • maybe look for the right files in master instead?
    • validate on the title instead (using whatever title the learner chose)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions