Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
M
mailchimpsync
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Extensions
  • mailchimpsync
  • Issues
  • #5

Closed
Open
Opened Jan 15, 2020 by Rich@artfulrobotMaintainer

Add `skip_merge_validation` to api calls

skip_merge_validation

There's a problem when someone sets a merge field as Required because then we're not allowed to not submit that merge field when changing subscriptions etc.

This parameter seems sensible to use.

Also requires documentation update.

Edited Jan 15, 2020 by Rich
Assignee
Assign to
First release
Milestone
First release
Assign milestone
Time tracking
None
Due date
None
Reference: extensions/mailchimpsync#5