Check PHPStan in addons #1592
No reviewers
Labels
No labels
2018.09
2019.01
2019.03
2019.06
2019.09
2019.12
2020.03
2020.06
2020.09
2020.12
2021.03
2021.07
2021.09
2022.02
2022.06
2022.09
2022.12
2023.04
2023.05
2023.09
2024.03
2024.06
2024.09
2024.12
2025.02
2025.05
dependencies
Hackathon 2021
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: friendica/friendica-addons#1592
Loading…
Reference in a new issue
No description provided.
Delete branch "Art4/friendica-addons:fix-phpstan-error"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I noticed that #1589 adds a PHPStan warning that was not noticed in the review. This leads now to failing tests in the friendica repository.
This PR fixes the error and tries to introduce PHPStan tests in the addon repository to avoid this situation in the future.
Update 1: In the meanwhile #1590 was merged. I resolved the merge conflict.
Update 2: And now I noticed #1591 😆
Concerning the warning: Couldn't the addons be excluded from that? Because currently this leads to a situation where you have to fix something in the addons to make the core work - and this doesn't sound right.
I'm currently getting a merge conflict when I try to accept rhe PR.
This warning occurs because we don't have checks on the addon repository. If we had this check established, we wouldn't run into this situation.
The addon repository depends on the friendica repository. That's why we a.) run checks in friendica repository so a breaking change there should notified early and b.) should run checks on the addon repository to avoid situations like #1589.
As long as we don't have a documented contract or other mechanisms between these repos I recommend that we keep this checks.
I cannot see if woodpecker jobs are running on this repository. Are the actions configured correctly and activated?
27c3572a96
to7a7940a8ed
@MrPetovan I'm a bit confused. Are actions and runners are activated in this repo?
It doesn't look like it but I don't pay attention to it. Maybe @nupplaPhil would be able to answer this question better.
IIRC the CI only allowes one target - github or self-hosted service - and as long as the bug that prevents us from importing the core repos history and issues is not solved upstream, we are bound to check either core or addons.
Ok, thank you for this information. This seems to be a problem. And as long as we couldn't run the CI on the addons only we should definitely keep the tests running for the addons in the friendica repository.