Skip to content
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 #8756: doc: extra-source-files are tracked by cabal build (backport #8765) #8814

Merged
merged 1 commit into from
Feb 25, 2023

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Feb 25, 2023

This is an automatic backport of pull request #8765 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

Copy link
Member

@Mikolaj Mikolaj left a comment

Choose a reason for hiding this comment

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

Doc only.

@Mikolaj Mikolaj added the merge me Tell Mergify Bot to merge label Feb 25, 2023
)

Changing a file from `extra-source-files` causes `cabal build` to
reevaluate the build plan, judging from the following behavior.

```console
$ cabal build
...

$ cabal build
Up to date

  # Make a change to any of the extra-source-files, e.g. Foo.txt

$ cabal build
...
In order, the following would be built (use -v for more details):
 - ... (lib) (file Foo.txt changed)
...
```

One notes here that the 3rd `cabal build` does not just output "Up to date".

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
(cherry picked from commit fdcf77b)
@mergify
Copy link
Contributor Author

mergify bot commented Feb 25, 2023

⚠️ This pull request got rebased on behalf of a random user of the organization.
This behavior will change on the 1st February 2023, Mergify will pick the author of the pull request instead.

To get the future behavior now, you can configure bot_account options (e.g.: bot_account: { author } or update_bot_account: { author }.

Or you can create a dedicated github account for squash and rebase operations, and use it in different bot_account options.

@mergify mergify bot merged commit 3986ee1 into 3.10 Feb 25, 2023
@mergify mergify bot deleted the mergify/bp/3.10/pr-8765 branch February 25, 2023 09:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport merge me Tell Mergify Bot to merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants