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

Make Build models default to triggered #8031

Merged
merged 8 commits into from
Jan 30, 2023
Merged

Conversation

ericholscher
Copy link
Member

I'm not sure why we were defaulting them to Finished,
but this should help not confuse the badge code,
and just be more correct in general.

Copy link
Member

@stsewd stsewd left a comment

Choose a reason for hiding this comment

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

Looks like tests need to be updated, this also discovered a bug (just a missing none check) :D

btw, we already change the value to triggered

build = Build.objects.create(
project=project,
version=version,
type='html',
state=BUILD_STATE_TRIGGERED,
success=True,
commit=commit
)
but better to have it by default.

@humitos
Copy link
Member

humitos commented May 25, 2021

@ericholscher it would be good to finish this PR and merge it when you have some time. It seems there is some tests failing due to the change.

@ericholscher
Copy link
Member Author

@humitos feel free to finish it up if you have bandwidth. I don't think I'll have time for a little while, unfortunately.

@stale
Copy link

stale bot commented Jul 21, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Status: stale Issue will be considered inactive soon label Jul 21, 2021
@ericholscher ericholscher added the Accepted Accepted issue on our roadmap label Jul 21, 2021
@stale stale bot removed the Status: stale Issue will be considered inactive soon label Jul 21, 2021
ericholscher and others added 2 commits February 17, 2022 12:03
I'm not sure why we were defaulting them to Finished,
but this should help not confuse the badge code,
and just be more correct in general.
@ericholscher ericholscher requested a review from a team as a code owner February 17, 2022 15:12
@ericholscher ericholscher added the Good First Issue Good for new contributors label Mar 8, 2022
@humitos
Copy link
Member

humitos commented Jul 19, 2022

I'm adding this PR to the Roadmap Q3 so we can finish it. It would be good to have our data being consistent.

@humitos
Copy link
Member

humitos commented Aug 29, 2022

@stsewd would you like (if you have some time 😄 ) to take a look at this PR and update it so we can move forward and merge it? 🙏🏼

Copy link
Member

@stsewd stsewd left a comment

Choose a reason for hiding this comment

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

Did a quick test locally, I didn't see anything weird.

Copy link
Member Author

@ericholscher ericholscher left a comment

Choose a reason for hiding this comment

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

👍 Can't approve this since I originally opened it, but looks great. Thanks for pushing this to done!

@ericholscher ericholscher merged commit 9cc3c36 into main Jan 30, 2023
@ericholscher ericholscher deleted the build-default-triggered branch January 30, 2023 23:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accepted Accepted issue on our roadmap Good First Issue Good for new contributors
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants