Skip to content

GitHub pull request template #2973

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

Merged
merged 1 commit into from
Sep 18, 2018
Merged

Conversation

tautschnig
Copy link
Collaborator

The template provides guidance and a check-list to submitters to make sure code
reviews can be as efficient as possible.

Thank you for your contribution. Please make sure your pull request fulfils all of the below requirements. If you cannot currently tick all the boxes, but would still like to create a PR, then add the label "work in progress" and assign the PR to yourself.
--->

- [ ] Each commit message has a non-empty body, answering the "Why?" question.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"...explaining why the change was made"?

--->

- [ ] Each commit message has a non-empty body, answering the "Why?" question.
- [ ] My contribution is formatting in line with CODING_STANDARD.md.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is formatted


- [ ] Each commit message has a non-empty body, answering the "Why?" question.
- [ ] My contribution is formatting in line with CODING_STANDARD.md.
- [ ] Methods or procedures I have added are documented.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

...using Doxygen comments at the definition site (not the declaration)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have included a reference to CODING_STANDARD.md.

- [ ] Each commit message has a non-empty body, answering the "Why?" question.
- [ ] My contribution is formatting in line with CODING_STANDARD.md.
- [ ] Methods or procedures I have added are documented.
- [ ] Regression or unit tests are included, or existing tests cover the modified code.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(and I say which ones)

The template provides guidance and a check-list to submitters to make sure code
reviews can be as efficient as possible.
Copy link
Contributor

@allredj allredj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR failed Diffblue compatibility checks (cbmc commit: caf1f5f).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/85118287
Status will be re-evaluated on next push.
Please contact @peterschrammel, @thk123, or @allredj for support.

Common spurious failures:

  • the cbmc commit has disappeared in the mean time (e.g. in a force-push)
  • the author is not in the list of contributors (e.g. first-time contributors).

@tautschnig
Copy link
Collaborator Author

I am going to merge this once CI passes, despite the TG compatibility check failing: I have no idea why a non-code change should be causing this and thus assume it was broken before already.

Copy link
Contributor

@allredj allredj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Passed Diffblue compatibility checks (cbmc commit: 9a56f42).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/85120424

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants