The default value oflines.markeredgecolor'auto' which means "follow the color", but when setting it to a color it stops following the color of the line.

This is the correct fix.

@useidemaisachola Thank you for this fix and the test! If you can clean up the linting/whitespace issues I think this can be merged straight away.

@tacaswell ok, i can solve them! One question as this is my first PR - after i resolve the problems with the spaces i have to commit and open another PR? Or it's possible to still use this one?

You should continue on your branch, and pushing it here will update this PR.

@QuLogic Ok, thank you!

@tacaswell I resolved the problem with the spaces! Now it's giving some kind of error with the version of python on windows... It is something that i have to change?

@useidemaisachola that Azure Windows test can be flakey. The failure is not caused by your change. I have re-run it to see if we can be lucky the second time.

so, now i have to resolve the conflits?

so, now i have to resolve the conflits?

Yes, but if you are not comfortable doing that we can handle it for you. It looks like you and and another recent PR have added new tests in the same place, so it's just a case of making sure we keep both.

Already resolved the conflit but I guess i leaved an extra line at the end of the file or something like that, because it's failing one test... it's that?

I took the liberty to remove the extra line at the end. Tests should pass now.

ok, thank you for the tips and the help!

I have to enter the suggestion that you told me or it´s already changed in the repository?

You'll have to apply it yourself, either locally and push, or using the UI here.

ok, it gave an error but I will fix it.

I think everything it´s ok now.

Now i have to do close or something like that?

No. You don't have to do anything. We have policy that each PR needs two approvals by core developers. So, we're just waiting for a second review.

Ok, thank you.

Thanks@useidemaisachola! Congratulations on your first PR to Matplotlib 🎉 We hope to hear from you again.

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

git checkout v3.10.xgit pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

git cherry-pick -x -m1 20bdd72d3cb9a4a93657091d80fdeb9d0089609c

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am "Backport PR #29895: The 'lines.markeredgecolor' now doesn't interfere on the color of errorbar caps "

4. Push to a named branch:

git push YOURFORK v3.10.x:auto-backport-of-pr-29895-on-v3.10.x

5. Create a PR against branch v3.10.x, I would have named this PR:

"Backport PR#29895 on branch v3.10.x (The 'lines.markeredgecolor' now doesn't interfere on the color of errorbar caps )"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove theStill Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free tosuggest an improvement.

@QuLogic Thank you so much! So can I delete already the branch? The lumberbot gave some kind of feedback...

@useidemaisachola you can safely delete your branch. Your work is now in Matplotlib'smain branch and lumberbot is here to help us get it also into ourv3.10.x branch (which we will use for the next micro release).
https://matplotlib.org/devdocs/devel/pr_guide.html#backport-strategy

Ok, thank you!