GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Should an issue be created first, before the Pull Request? · Issue #104 · python/devguide

Should an issue be created first, before the Pull Request? #104

New issue
Copy link
New issue
Copy link
Closed
Closed
Should an issue be created first, before the Pull Request?#104
Copy link

Description

@Mariatta
Mariatta
opened on Feb 11, 2017
Issue body actions

In the Quick Start section of the Dev Guide:

5. Make a pull request.

6. Create an issue on the issue tracker if one does not already exist.

Just wondering if it might be better if an issue be created first (in bpo) before the pull request?
This way Pull Request can be created with bpo-NNNN: in the PR title as well as the commit message.

Activity

  1. Mariatta
    added
    question
    on Feb 11, 2017
  2. ezio-melotti commented on Feb 11, 2017

    @ezio-melotti
    ezio-melotti
    on Feb 11, 2017
    Member
    More actions

    Maybe we could even leave this out from the quick start, in most of the cases there is already an issue, or one is created beforehand in order to discuss the details of the fix. Eventually we might also automate the issue creation for PR that don't refer to any existing issue.

  3. matrixise commented on Feb 11, 2017

    @matrixise
    matrixise
    on Feb 11, 2017
    Member
    More actions

    Or just add "If there is no issue, create it before the PR and note the PR with "bpo-ISSUENUMBER Description".

  4. berkerpeksag commented on Feb 11, 2017

    @berkerpeksag
    berkerpeksag
    on Feb 11, 2017
    Member
    More actions

    We should also mention that there is no need create an issue for trivial changes like typo fixes.

  5. ncoghlan
    closed this as completedin #109on Feb 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.