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
As a developer,
When I run my tests,
And use fern for reporting,
And have committed changes
Then the git sha should be a tag or a column in the report
For unpushed change,
We need to make a decision on what to show. Maybe as a "dirty" as we have no way to referring back to the changes if the commit is not pushed or if the files are not committed in the first place
The text was updated successfully, but these errors were encountered:
Thats a good point @jjchambl about large number of local tests. I think we need to evolve this such that we can configure the server to be using a flag to accept a dirty report or not. That way if people want to use for local tests, they can run the fern-reporter locally with --dirty-enabled or something like that so that it would accept those type of reports
As a developer,
When I run my tests,
And use fern for reporting,
And have committed changes
Then the git sha should be a tag or a column in the report
For unpushed change,
We need to make a decision on what to show. Maybe as a "dirty" as we have no way to referring back to the changes if the commit is not pushed or if the files are not committed in the first place
The text was updated successfully, but these errors were encountered: