Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make keyword expression matching case-insensitive #6316

Merged
merged 8 commits into from Dec 12, 2019
Merged

Make keyword expression matching case-insensitive #6316

merged 8 commits into from Dec 12, 2019

Commits on Dec 5, 2019

  1. Change -k EXPRESSION matching to be case-insensitive

    @cb109
    cb109 committed Dec 5, 2019
    Copy the full SHA
    e24b6b0 View commit details
    Browse the repository at this point in the history

  2. Update docs about case-insensitive expression matching

    @cb109
    cb109 committed Dec 5, 2019
    Copy the full SHA
    ac5929e View commit details
    Browse the repository at this point in the history

  3. Update authors file and sort the list

    @cb109
    cb109 committed Dec 5, 2019
    Copy the full SHA
    24d4882 View commit details
    Browse the repository at this point in the history

  4. Add changelog file for PR 6316

    @cb109
    cb109 committed Dec 5, 2019
    Copy the full SHA
    5a7de2c View commit details
    Browse the repository at this point in the history

  5. Update doc/en/example/markers.rst 

    Co-Authored-By: Bruno Oliveira <nicoddemus@gmail.com>
    @cb109 @nicoddemus
    cb109 and nicoddemus committed Dec 5, 2019
    Copy the full SHA
    623b398 View commit details
    Browse the repository at this point in the history

  6. Add a failing test to ensure not everything matches by accident

    @cb109
    cb109 committed Dec 5, 2019
    Copy the full SHA
    a326fa2 View commit details
    Browse the repository at this point in the history

Commits on Dec 6, 2019

  1. Iterate a generator expression instead of a temporary list 

    Co-Authored-By: Bruno Oliveira <nicoddemus@gmail.com>
    @cb109 @nicoddemus
    cb109 and nicoddemus committed Dec 6, 2019
    Copy the full SHA
    3a0f436 View commit details
    Browse the repository at this point in the history

  2. Replace 'removal' by 'breaking' changelog category 

    As discussed, sometimes we will need to introduce changes
which are not necessarily removals but might break existing
suites
    @nicoddemus
    nicoddemus committed Dec 6, 2019
    Copy the full SHA
    c6ed69a View commit details
    Browse the repository at this point in the history