-
Notifications
You must be signed in to change notification settings - Fork 264
chore(ci): get rid of dirty flag #6677
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
Conversation
Jenkins BuildsClick to see older builds (21)
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #6677 +/- ##
========================================
Coverage 59.77% 59.77%
========================================
Files 805 805
Lines 114125 114125
========================================
+ Hits 68213 68221 +8
+ Misses 38948 38918 -30
- Partials 6964 6986 +22
Flags with carried forward coverage won't be shown. Click here to find out more.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hm. But what's wrong with it? It was there for a reason 🤔
|
@siddarthkay do we still want this merged? Or should we close it? |
7bb33fe to
46e9b2c
Compare
|
@igor-sirotin : still relevant, was just ignored by me for long. "dirty" has no business being in version and is often confusing when this version reaches status-desktop via status-go |
46e9b2c to
b395b37
Compare
b395b37 to
d165cf8
Compare
Summary
I found few instances of
--dirtyin status-go as well,Now that we don't have this versioning in status-desktop it would be consistent if we removed it from here as well.