Avoid warnings in addons #639

Merged

annando merged 11 commits from warnings into develop

annando commented (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.

👍 1

annando commented (Migrated from github.com)

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

MrPetovan (Migrated from github.com) requested changes

annando commented (Migrated from github.com)

I guess most notices had been solved now.

MrPetovan (Migrated from github.com) approved these changes

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

No reviewers

No Label

No Milestone

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Loading…

There is no content yet.

Labels Milestones

Avoid warnings in addons #639

Reviewers

Step 1:

Step 2: