Changing Naubotot data in a branch associated with a PR should count as a change in the PR.
Currently Nautobot can send a webhook if a PR is created/updated/deleted. The only way to 'update' a PR currently is to edit the PR and change the title or description (which is not practical)
Having a change in the data in a branch associated with a PR count as a change in the PR would be helpful in a CI pipeline:
Currently Nautobot can send a webhook if a PR is created
If the CI tests fail, the PR can be updated by the CI system
Once the PR submitter realizes there's a problem with the data, they can fix the data that caused the failure
This is where the CI pipeline should run again (just like in GitHub) and report the results
after talking with @jedelman8 , closing this out for now so we can talk through how we want to manage the PRs and trigger webhooks (what events, mechanics, etc)
Changing Naubotot data in a branch associated with a PR should count as a change in the PR.
Currently Nautobot can send a webhook if a PR is created/updated/deleted. The only way to 'update' a PR currently is to edit the PR and change the title or description (which is not practical)
Having a change in the data in a branch associated with a PR count as a change in the PR would be helpful in a CI pipeline: