Avoid warnings in addons #639

Merged
annando merged 11 commits from warnings into develop 5 years ago
annando commented 5 years ago (Migrated from github.com)

And here the same for the addons. I hadn't changed any styling issue by purpose, since we still have a huge open PR - and I want to avoid merge conflicts.

And here the same for the addons. I hadn't changed any styling issue by purpose, since we still have a huge open PR - and I want to avoid merge conflicts.
annando commented 5 years ago (Migrated from github.com)

The common processes don't generate warnings or notices any more.

The common processes don't generate warnings or notices any more.
MrPetovan (Migrated from github.com) requested changes 5 years ago
annando commented 5 years ago (Migrated from github.com)

I guess most notices had been solved now.

I guess most notices had been solved now.
MrPetovan (Migrated from github.com) approved these changes 5 years ago

Reviewers

The pull request has been merged as 475299e642.
You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.
git checkout -b warnings develop
git pull origin warnings

Step 2:

Merge the changes and update on Forgejo.
git checkout develop
git merge --no-ff warnings
git push origin develop
Sign in to join this conversation.
Loading…
There is no content yet.