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 — Feature: Enhance the visibility of the "Update branch button" section · Issue #1527 · python/devguide

Feature: Enhance the visibility of the "Update branch button" section #1527

New issue
Copy link
New issue
Copy link
Open
Open
Feature: Enhance the visibility of the "Update branch button" section#1527
Copy link
Labels
topic-pull requeststype-featureAdditions; New content or section neededAdditions; New content or section needed

Description

@StanFromIreland
StanFromIreland
opened on Mar 4, 2025
Issue body actions

Describe the enhancement or feature you would like

This is something I find myself informing new contributors about daily. It should be made more visible in some way. (Then there is the problem of increasing the viability of the devguide itself...)

For now I think it would be good to move the section to just below the submitting section rather than the bottom of the file.

Describe alternatives you have considered

No response

Additional context

No response

Activity

  1. StanFromIreland
    added
    type-featureAdditions; New content or section neededAdditions; New content or section needed
    on Mar 4, 2025
  2. StanFromIreland
    changed the title [-]Feature: Enhance the visibility of the "Update branch button"[/-] [+]Feature: Enhance the visibility of the "Update branch button" section[/+] on Mar 4, 2025
  3. zware commented on Mar 4, 2025

    @zware
    zware
    on Mar 4, 2025
    Member
    More actions

    I'm not clear on why this needs to move, or why it's being pointed out daily. The last point of the section is very relevant:

    Do not click Update branch without a good reason because it notifies everyone watching the PR that there are new changes, when there are not, and it uses up limited CI resources.

    In many cases, it's probably best that it not be used except by someone merging the PR.

    Reacted by Hugo van Kemenade and Zanie Blue
  4. StanFromIreland commented on Mar 6, 2025

    @StanFromIreland
    StanFromIreland
    on Mar 6, 2025
    MemberAuthor
    More actions

    It's being pointed out daily because new contributors are updating every time there is a new commit (e.g. the button appears)

    I just want the section to be moved to a more visible place so that it is read!

  5. zware commented on Mar 6, 2025

    @zware
    zware
    on Mar 6, 2025
    Member
    More actions

    Ahh, I see now!

    I wonder if a better solution might be for @bedevere-bot to watch for the merge commits created by the button, and complain if they look abusive (more than one in a row, more than one in a day, multiple without a diff, etc.).

  6. StanFromIreland commented on Mar 6, 2025

    @StanFromIreland
    StanFromIreland
    on Mar 6, 2025
    MemberAuthor
    More actions

    I posted in the docs discord about welcome-bot which would post a message when someone opens their first pr? Maybe that would work too?

  7. StanFromIreland
    added
    type-new content
    topic-pull requests
    type-featureAdditions; New content or section neededAdditions; New content or section needed
    and removed
    type-featureAdditions; New content or section neededAdditions; New content or section needed
    type-feature
    on Mar 3, 2026
  8. nyakoteysuzzy commented on Oct 13, 2026

    @nyakoteysuzzy
    nyakoteysuzzy
    on Oct 13, 2026
    More actions

    Hello, I am a beginner contributing to open source, and I would like to work on this issue.

    I noticed the discussion about moving the “Update branch button” section to make it more visible. Would moving the section below the “Submitting” section still be an acceptable solution, or would you prefer one of the alternatives discussed?

    I would appreciate your guidance before I begin working on it. Thank you!

  9. bennibyx commented on Oct 14, 2026

    @bennibyx
    bennibyx
    on Oct 14, 2026 · Hidden as low-quality
    show commentMore actions
  10. pavithraramesh5500-ship-cse commented on Oct 19, 2026

    @pavithraramesh5500-ship-cse
    pavithraramesh5500-ship-cse
    on Oct 19, 2026 · Hidden as low-quality
    show commentMore actions
  11. aftercoma commented on Nov 2, 2026

    @aftercoma
    aftercoma
    on Nov 2, 2026 · Hidden as low-quality
    show commentMore actions
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

    topic-pull requeststype-featureAdditions; New content or section neededAdditions; New content or section needed

    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.