Andrew Ardill

Something like that, you could also have text under that with something like: > Log in to comment The intent is to try and encourage visitors to add comments. Another...

That is very interesting, but yes I didn't notice at all. I don't think you need instructional text, but what I was thinking was prefixing the comment with the move...

I have tweaked the way enemies spawn to make the endgame a bit more winnable. It is at #3 if you want to check it out.

A nice option would be to allow signing in using GitHub or other OAuth providers. This could potentially tie in to publishing options down the track - save as a...

One option I have seen is to let the user add their email address, and then appropriate sign-in options appear dynamically. Not sure of the robustness of this, but might...

> From the [relevant docs](https://docs.dagster.io/guides/automate/declarative-automation/customizing-automation-conditions/customizing-eager-condition#respecting-data-versioning): > > import dagster as dg > > condition = dg.AutomationCondition.eager().replace( > "newly_updated", dg.AutomationCondition.data_version_changed() > ) > Looks like this issue can be closed? I've...

FYI here is the AutomationCondition I'm currently using. I had to split the `any_deps` checks to exclude my dbt source assets from triggering the `will_be_requested` condition. Seems to be mostly...

Hey @danielgafni, this is copied from the built-in eager condition. The idea is to select all the assets that will need to be refreshed based on this data updating. If...

I think that is a valid critique in general. For my case (and I suppose this would be common) I know that if the source data version has changed then...

Reminds me I should add a condition for code changes :) Out of interest, how are ou defining data versions and how are you setting up observations on sources (if...