Skip to content

Conversation

@Riksu9000
Copy link
Contributor

@Riksu9000 Riksu9000 commented Aug 13, 2022

We can have multiple checks in one file as different jobs that get triggered with the same events. The main workflow should run when there are changes that may affect the builds.

Do you think the code formatting check should also be moved here? It has slightly different triggering events, but can be tweaked to work. (Maybe there isn't a good reason to do so)

@Riksu9000 Riksu9000 added this to the 1.11.0 milestone Aug 13, 2022
@JF002
Copy link
Collaborator

JF002 commented Aug 21, 2022

I think it makes sense that building the firmware, the simulator and checking the code formatting should be triggered at the same time, yes. So merging those 3 workflows in 1 totally make sense. I'll ask @Avamander and @NeroBurner opinion as (I think) they wrote those 2 additional workflows ;-)

Copy link
Contributor

@NeroBurner NeroBurner left a comment

Choose a reason for hiding this comment

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

as long as we see with the checks which of the jobs failed I'm OK with the change

@Riksu9000
Copy link
Contributor Author

I'll merge this as I think we always want to build the firmware and the simulator at the same time.

@Riksu9000 Riksu9000 merged commit f53e750 into InfiniTimeOrg:develop Aug 25, 2022
@Riksu9000 Riksu9000 deleted the merge-ci branch August 25, 2022 05:32
@ghost ghost mentioned this pull request Aug 25, 2022
feduss pushed a commit to feduss/CustomInfiniTime that referenced this pull request Sep 11, 2022
minacode pushed a commit to minacode/InfiniTime that referenced this pull request Sep 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants