search

easystats / report

:scroll: :tada: Automated reporting of objects in R
https://easystats.github.io/report/
Other
694 stars 70 forks source link

Update `DESCRIPTION` to use latest 'easystats' dependencies #426

Closed github-actions[bot] closed 5 months ago

github-actions[bot] commented 5 months ago

Automatically updated the DESCRIPTION file using usethis::use_latest_dependencies().

IndrajeetPatil commented 5 months ago

@rempsyc Did you change some settings for this repo to make these two workflows as the required workflows?

rempsyc commented 5 months ago

Yes, I did. I see that in this case the tests are not triggered. I don't see how to trigger the tests automatically or manually in this case? But as maintainer I can bypass branch protections. I guess I will do this in this situation.

IndrajeetPatil commented 5 months ago

I'd really appreciate it if you discuss with the team before implementing new infrastructural measures. This is what I have done in the past in the easystats meta-package repo issues.

If the team thinks it's a good idea, we can implement for all repos. If the team thinks it's a bad idea, we don't implement for any repo.

This is just to keep the infrastructure of the entire ecosystem in sync with each other so that nobody is surprised when they want to contribute to a repo that they don't actively maintain. I hope that makes sense?

rempsyc commented 5 months ago

I see. I can change it back. The idea is because I noticed that PRs were often merged when checks were failing for valid reasons, so checks essentially became useless. So let's discuss? What do you think would be a good safeguard against this problem? Should we make some workflows mandatory across all repos?

rempsyc commented 4 months ago

@IndrajeetPatil I have turned off the required status checks for the report repo