You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When my issues are reported as fixed on GitHub,
I like to actually check the live site to verify that everything is now as I expect.
Unfortunately, there is a very noticeable delay of at least several hours
between the issue being fixed and the live site reflecting the changes.
This delay prevents me from immediately verifying the fixes and moving on from the issue, which is very annoying.
(I'm sure I'm not the only one who has noticed this and is annoyed with the inefficiency...)
I'm sure there are reasons for this related to the current pipeline (daily build?), but I see no fundamental reason why there couldn't be an incremental rebuild and update system that would translate to instantaneous updates in most cases at least.
Needless to say, accelerating the workflow for everyone would be very nice and productive...
The first step towards fixing this would be documenting all reasons why updates are not already nearly instantaneous...
At the very least, it would be nice to know how to determine the exact time at which we can expect updates to land on the live site.
The text was updated successfully, but these errors were encountered:
When my issues are reported as fixed on GitHub,
I like to actually check the live site to verify that everything is now as I expect.
Unfortunately, there is a very noticeable delay of at least several hours
between the issue being fixed and the live site reflecting the changes.
This delay prevents me from immediately verifying the fixes and moving on from the issue, which is very annoying.
(I'm sure I'm not the only one who has noticed this and is annoyed with the inefficiency...)
I'm sure there are reasons for this related to the current pipeline (daily build?), but I see no fundamental reason why there couldn't be an incremental rebuild and update system that would translate to instantaneous updates in most cases at least.
Needless to say, accelerating the workflow for everyone would be very nice and productive...
The first step towards fixing this would be documenting all reasons why updates are not already nearly instantaneous...
At the very least, it would be nice to know how to determine the exact time at which we can expect updates to land on the live site.
The text was updated successfully, but these errors were encountered: