-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(postbuildstepper): only create PR#channel for configured source branches #195
Conversation
37f9a99
to
6fe021d
Compare
6fe021d introduces the test to expose the bug this repo isn't configured to run the cargo tests yet. here's the result from the local run:
the integration test did fail on CI
f5f9c46 introduces the bugfix |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! Good catch ..and nice test addition. :) I just left one question/optional suggestion. This is good to merge either way.
|
||
Ok(maybe_channel_names) | ||
} else { | ||
Ok(None) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add some kind of log or notification hook for whenever this occurs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there's a debug!
one that prints this further up.
and the call to create_channel_artifacts
has info!
level messages for artifacts that are actually created.
do you think that's sufficient?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I saw the debug a bit earlier, which could be fine for now... but depending on how long we need to support the legacy channels, it might be nice to have some other mechanism that notifies us more directly or loudly than developer logs, such as push messages, or emails via a monitoring tool like Grafana or Sentry or even a mm plugin, etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it might be nice to have some other mechanism that notifies us more directly or loudly than developer logs, such as push messages, or emails via a monitoring tool like Grafana or Sentry or even a mm plugin, etc.
agreed, however out of scope for this bugfix PR.
testing the previously existing bug where a channel would be created for a PR by its number despite the channel name not being configured as a channel source branch.
…ranches previously it would create a channel for every PR
6fe021d
to
eb8d5fb
Compare
previously it would create a channel for every PR
cc @alastairong1