CompFuzzCI integration (no forks) #5697
Conversation
| branches: | ||
| - master | ||
| types: [opened, closed, synchronize, reopened] | ||
| issues: |
There was a problem hiding this comment.
Why is issues here? Why should this trigger when someone makes an issue?
There was a problem hiding this comment.
It's for keeping track of active bugs in dafny. If the fuzzer finds the bug that has already been reported in some issue, it can ignore that bug.
Should I put issue processing in a separate workflow?
| @@ -0,0 +1,91 @@ | |||
| name: CompFuzzCI | |||
There was a problem hiding this comment.
Could you add a comment to the top of this file that explains what it does?
There was a problem hiding this comment.
Good idea. I'll get that done. Thanks!
| pull_request: | ||
| branches: | ||
| - master | ||
| types: [opened, closed, synchronize, reopened] |
There was a problem hiding this comment.
What is the types list for?
There was a problem hiding this comment.
I want to trigger workflow on pull request getting closed as well, this does not happen by default, hence the list.
By default pull_request event trigger on pull request being opened, synced, reopened.
### Description <!-- Is this a user-visible change? Remember to update RELEASE_NOTES.md --> <!-- Is this a bug fix for an issue visible in the latest release? Mention this in the PR details and ensure a patch release is considered --> ### How has this been tested? <!-- Tests can be added to `Source/IntegrationTests/TestFiles/LitTests/LitTest/` or to `Source/*.Test/…` and run with `dotnet test` --> <small>By submitting this pull request, I confirm that my contribution is made under the terms of the [MIT license](https://github.com/dafny-lang/dafny/blob/master/LICENSE.txt).</small>
Description
How has this been tested?
By submitting this pull request, I confirm that my contribution is made under the terms of the MIT license.