new exercise - series

[GroophyLifefor]

No description provided.

[github-actions]

This PR touches files which potentially affect the outcome of the tests of an exercise. This will cause all students' solutions to affected exercises to be re-tested.

If this PR does not affect the result of the test (or, for example, adds an edge case that is not worth rerunning all tests for), please add the following to the merge-commit message which will stops student's tests from re-running. Please copy-paste to avoid typos.

[no important files changed]

For more information, refer to the documentation. If you are unsure whether to add the message or not, please ping @exercism/maintainers-admin in a comment. Thank you!

[GroophyLifefor]

[no important files changed]

[GroophyLifefor]

it seems to be triggered because I edited the test file of another exercise, if you look at the changes I edited a simple comment line, there is no problem

[ErikSchierboom]

it seems to be triggered because I edited the test file of another exercise, if you look at the changes I edited a simple comment line, there is no problem

Just to be clear what the above message means. If this PR is merged, the fact that a test file was updated would mean all of its solutions would have to be rerun in the test runner. Whilst the track is currently not yet live, this doesn't yet matter, but it will be important once it is live. The fact that it is "just a comment" is not something we can detect, so we'd have to rerun the solutions. However, you, the maintainer, can identify that it is "just a comment", in which case rerunning the tests wouldn't change any outcome. If this is true, you should add the [no important files changed] text to the commit message (you can add it when you get the commit text after pressing on Squash and merge).

See https://exercism.org/docs/building/tracks#h-avoiding-triggering-unnecessary-test-runs for more information.

[GroophyLifefor]

it seems to be triggered because I edited the test file of another exercise, if you look at the changes I edited a simple comment line, there is no problem

Just to be clear what the above message means. If this PR is merged, the fact that a test file was updated would mean all of its solutions would have to be rerun in the test runner. Whilst the track is currently not yet live, this doesn't yet matter, but it will be important once it is live. The fact that it is "just a comment" is not something we can detect, so we'd have to rerun the solutions. However, you, the maintainer, can identify that it is "just a comment", in which case rerunning the tests wouldn't change any outcome. If this is true, you should add the [no important files changed] text to the commit message (you can add it when you get the commit text after pressing on Squash and merge).

See https://exercism.org/docs/building/tracks#h-avoiding-triggering-unnecessary-test-runs for more information.

Thanks you so much, I got it.