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.

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

Release v1.1.0 that adds a new softmask parameter, to optionally keep original softmasking #16

Merged
merged 10 commits into from
Oct 9, 2024

Commits on Sep 26, 2024

  1. Configuration menu
    Copy the full SHA
    a6651c0 View commit details
    Browse the repository at this point in the history

Commits on Sep 27, 2024

  1. Configuration menu
    Copy the full SHA
    d22dd86 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    65e8298 View commit details
    Browse the repository at this point in the history

Commits on Sep 29, 2024

  1. Update usage.md because I need to make an extra commit

    Quoted (emphasis mine) from: https://github.com/nf-core/pairgenomealign/actions/runs/11063552525/job/30739852990?pr=15
    
    > It looks like this pull-request is has been made against the [oist/LuscombeU_nfcore_pairgenomealign_fork](https://github.com/oist/LuscombeU_nfcore_pairgenomealign_fork) `master` branch.
    >  The `master` branch on nf-core repositories should always contain code from the latest release.
    >  Because of this, PRs to `master` are only allowed if they come from the [oist/LuscombeU_nfcore_pairgenomealign_fork](https://github.com/oist/LuscombeU_nfcore_pairgenomealign_fork) `dev` branch.
     > 
     > You do not need to close this PR, you can change the target branch to `dev` by clicking the _"Edit"_ button at the top of this page.
    >  **Note that even after this, the test will continue to show as failing until you push a new commit.**
    charles-plessy authored Sep 29, 2024
    Configuration menu
    Copy the full SHA
    3063a19 View commit details
    Browse the repository at this point in the history
  2. Fix Markdown file.

    I always forget.  That it is forbidden in nf-core pipeline to have
    two spaces separating two sentences.
    charles-plessy committed Sep 29, 2024
    Configuration menu
    Copy the full SHA
    064dae4 View commit details
    Browse the repository at this point in the history

Commits on Oct 1, 2024

  1. Update docs/usage.md

    Co-authored-by: Matthias Hörtenhuber <[email protected]>
    charles-plessy and mashehu authored Oct 1, 2024
    Configuration menu
    Copy the full SHA
    ce67bc0 View commit details
    Browse the repository at this point in the history
  2. Update nextflow_schema.json

    Co-authored-by: Matthias Hörtenhuber <[email protected]>
    charles-plessy and mashehu authored Oct 1, 2024
    Configuration menu
    Copy the full SHA
    4ce0278 View commit details
    Browse the repository at this point in the history

Commits on Oct 2, 2024

  1. Merge pull request #15 from oist/dev

     Release v1.1.0 that adds a new softmask parameter, to optionally keep original softmasking.
    charles-plessy authored Oct 2, 2024
    Configuration menu
    Copy the full SHA
    faa346c View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    3503b2b View commit details
    Browse the repository at this point in the history

Commits on Oct 9, 2024

  1. Spelling

    Co-authored-by: Anabella Trigila <[email protected]>
    charles-plessy and atrigila authored Oct 9, 2024
    Configuration menu
    Copy the full SHA
    6974029 View commit details
    Browse the repository at this point in the history