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

Update --isuptodate documentation #584

Merged
merged 1 commit into from
Jan 19, 2025
Merged

Conversation

Tsingis
Copy link
Contributor

@Tsingis Tsingis commented Sep 21, 2024

As requested in #582

@Tsingis
Copy link
Contributor Author

Tsingis commented Oct 2, 2024

@erikbra Btw how should this work with scripts marked EVERYTIME.

Outputs whether the database is up to date or not (whether any non-everytime scripts would be run)

If there's even single one script marked as EVERYTIME, then --isuptodate never says database is up to date. I find this somewhat confusing behavior when everything has run successfully but database is not up to date.

@@ -37,7 +37,6 @@ Rebuilding a decade old product from scratch takes time, and features have to be
Expect this list to shrink over time.

- `--defaultencoding`
- `--isuptodate`
Copy link
Owner

Choose a reason for hiding this comment

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

One down here <3

@erikbra
Copy link
Owner

erikbra commented Jan 19, 2025

Perfect, thanks a lot, @Tsingis ! (sorry for the insanely long feedback time here)

@erikbra erikbra merged commit 5e5c178 into erikbra:main Jan 19, 2025
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.

2 participants