Closed lapineige closed 2 years ago
I propose to first merge that PR and later do 2.4.2 upgrade
!testme
I propose to first merge that PR and later do 2.4.2 upgrade
That's also what I had in mind. It's safer this way :)
We will need #120.
!testme
~Well, another CI for zero code change ? 😅~ My bad, I missed your commits.
Upgrade tested successfully 🙂
~Well, another CI for zero code change ? 😅~
As we have seen with pixelfed, better to have too much CI tests than not enough :p
My bad, I missed your commits.
Upgrade tested successfully 🙂
Can we merge ?
Apply last example_ynh
Cleanup backup
Update Readme : add templates #120
PR Status
Validation
Minor decision
Please replace '-NUM-' in this link by the PR number.
When the PR is marked as ready to merge, you have to wait for 3 days before really merging it.