When a repo requires linear history

[buddybu]

My team has a requirement that each repo has a linear history. This action seems to create merge commits which violates that requirement. Currently I have added a branch exception to this rule, but I was wondering if there was a way to configure the action to create rebase commits?

remote:
remote: - This branch must not contain merge commits.
remote: Found 1 violation:
remote:
remote: de1c782692ed1a20f1cc3343b9ac8977dd20961e
remote:

here is the action config:

    - name: Create Pull Request
      uses: peter-evans/create-pull-request@v7
      with:
        token: ${{ steps.generate_token.outputs.token }}
        title: Synchronizing with Crowdin
        body: |
          Automated changes by Crowdin CI

          Updated translation source POT files by extracting strings from the top of development
          Updated translation PO files with ones downloaded from Crowdin
        commit-message: |
          Synchronizing with Crowdin

          Rev Notes
          - Updated translations
        committer: Crowdin CI <crowdin@github-action>
        author: Crowdin CI <crowdin@github-action>
        branch: crowdin-translations
        delete-branch: true
        base: development

[Malix-Labs]

It would require a new input

However, I am not convinced that the current way that options passing are implemented (duplicating inputs) is superior to just making a single passthrough input, equivalent to -- for CLIs