Update support link

[sempruijs]

Pull Request Checklist

• I read the contributing guide
• Pull request contains a changelog file in ./changelog.d
• Pull request includes a sign off

[sempruijs]

Signed-off-by: Sem Pruijs sem@pruijs.net

[sempruijs]

Can someone help me a hand? I created a fork of the repo, created a new branch and made changes on that branch. Then I pushed to that branch the my fork. Now when I open this pr I see commits from another pr that I did earlier, but GitHub only shows in the file changes the actual changes that I did.

In the pr there are 7 commits, but I actually only did 2 on this branch. How did this happen?

[pixlwave]

For every new change you make, you should create a new branch from develop. You can fix this PR by

• Creating a new branch called say update-support-link-2 from develop
• Cherry pick the commits from update-support-link you would like to keep for this PR.
• Double check you did this correctly.
• Delete the update-support-link branch
• Rename update-support-link-2 to update-support-link
• Force push the update-support-link branch.

Doing all of this with a git GUI client will be the easiest way to do so.

And then from that point onwards, remember to branch from develop before you start a new piece of work 😃

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (eed031c) 51.68% compared to head (64e9b28) 51.68%.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop     #668   +/-   ##
========================================
  Coverage    51.68%   51.68%           
========================================
  Files          263      263           
  Lines        14310    14310           
  Branches      9133     9133           
========================================
  Hits          7396     7396           
  Misses        6691     6691           
  Partials       223      223           

Flag	Coverage Δ
unittests	20.66% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[sempruijs]

@pixlwave thank you for your help. Learned allot about git. It's good to go now

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[stefanceriu]

lgtm 👍