Best Practices for Branch Protection

แชร์
ฝัง
  • เผยแพร่เมื่อ 14 ธ.ค. 2024

ความคิดเห็น • 11

  • @CoderDave
    @CoderDave  4 ปีที่แล้ว +3

    ✨ *Question of the day* ✨: do you follow any other best practice?

  • @theneologic474
    @theneologic474 2 ปีที่แล้ว +2

    I had to watch it twice cause it had so much useful information! Thank you!

    • @CoderDave
      @CoderDave  2 ปีที่แล้ว

      Glad it was helpful!

  • @dev_mastery43
    @dev_mastery43 3 หลายเดือนก่อน +1

    can you please perform these steps practically that you showed in slides so it could be more easy for us to understand?

    • @CoderDave
      @CoderDave  3 หลายเดือนก่อน

      I will see what I can do :) I am planning on a new video on this because GitHub has introduced a number of changes since this vide

  • @Xannaria
    @Xannaria 2 ปีที่แล้ว +1

    Thanks for the video. 🙂How can I prevent for all members ability for deleting any brunches?

    • @CoderDave
      @CoderDave  2 ปีที่แล้ว

      The only way to disable someone to delete branches is to not give them Write access :(

  • @sandyj342
    @sandyj342 ปีที่แล้ว

    Excellent video Dave!

    • @CoderDave
      @CoderDave  ปีที่แล้ว

      Glad you liked it!

  • @sanjaypaudel3296
    @sanjaypaudel3296 2 ปีที่แล้ว +1

    s it possible to enable branch protection rules at the organisation level in Github so that all repositories part of that organisation inherit these rules for the applied branches. Right now its really a hassle to enable those same set of rules on a per repo basis for same set of branches.

    • @CoderDave
      @CoderDave  2 ปีที่แล้ว

      Unfortunately there is no organization level default option to set a branch protection for all repositories in an org. If this is something you don't want to repetitively do by hand, you can take a look at the GitHub API for Branch Protection... but you would need to script it yourself