ExportXMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Go Drivers
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      It's really easy to forget the merge priority rules when resolving a bug. Now that we are required to label a PR with bug / feature / etc, we should consider creating a followup hook that warns bug-labeled PRs if they are pointing at the master branch – more than likely they should be pointing at release/X.Y.

      Additionally, we could consider adding a checklist to the PR description for contributors to acknowledge if (1) they are working on a bug, and (2) if they are merging into the correct branch.

      We could also integrate with JIRA using a github workflow, if we could get credentials.

            Assignee:
            Unassigned
            Reporter:
            Preston Vasquez
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: