Skip to content

Follow up on PR for fixing tests (mostly styling)#2180

Merged
polarathene merged 1 commit intomasterfrom
follow-up-fix-tests
Sep 11, 2021
Merged

Follow up on PR for fixing tests (mostly styling)#2180
polarathene merged 1 commit intomasterfrom
follow-up-fix-tests

Conversation

@georglauterbach
Copy link
Copy Markdown
Member

Description

Just a follow up on #2177 with suggestions from @polarathene.

Type of change

  • Improvement (non-breaking change that does improve existing functionality)

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation (README.md or the documentation under docs/)
  • If necessary I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

@georglauterbach georglauterbach added priority/low area/tests kind/improvement Improve an existing feature, configuration file or the documentation labels Sep 11, 2021
@georglauterbach georglauterbach added this to the v10.2.0 milestone Sep 11, 2021
@georglauterbach georglauterbach self-assigned this Sep 11, 2021
@polarathene polarathene merged commit 8e91251 into master Sep 11, 2021
@polarathene polarathene deleted the follow-up-fix-tests branch September 11, 2021 12:43
@polarathene
Copy link
Copy Markdown
Member

@NorseGaud what did you do to trigger those commit references? They tag me via notification because my username is mentioned, and likewise the PR reference (no notification for me) appears on this PR and referenced one.

Is this something Github is doing when you updated a branch/PR of yours?

@NorseGaud
Copy link
Copy Markdown
Member

@polarathene Woh... I actually don't know... I've never seen these before. Very strange...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/tests kind/improvement Improve an existing feature, configuration file or the documentation priority/low

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants