Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Have Travis ensure that what's new is updated #10451

Copy link
Copy link
Closed
@jnothman

Description

@jnothman
Issue body actions

Sometimes when PRs are merged I waste time going back to double check that what's new has been updated.

We should make a travis run for PRs only that fails if tests are modified and what's new isn't modified. Perhaps we should even check that the diff to what's new mentions the current PR# (although there are sometimes exceptions to this).

Does this seem a reasonable policy?

Metadata

Metadata

Assignees

Labels

Build / CIEasyWell-defined and straightforward way to resolveWell-defined and straightforward way to resolve

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    Morty Proxy This is a proxified and sanitized view of the page, visit original site.