mirror/librenms-librenms
1
0
Fork 0
mirror of https://github.com/librenms/librenms.git synced 2024-10-07 16:52:45 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
librenms-librenms/doc/Developing/Merging-Pull-Requests.md
VVelox 6575042f5f go through making lots of the docs more lint happy (#10342) 
* clean up all but header incrementing in Creating-Transport.md

* make Device-Dependencies.md mdl happy

* make Entities.md as mdl happy as possible... one long table line left

* make mdl as happy as possible for index.md

* clean up Introduction.md as much as possible

* minor formatting cleanup... move each icon onto its own row

* make ack and notes the same style

* clean Macros.md up

* clean Rules.md up as much as possible

* tweak one line a bit to get it to format a bit nicer

* a bit more format tweaking, making sure it does not sure with >

* clean up as much as possible for Templates.md

* make Testing.md as mdl happy as possibly

* clean Transports.md up as much as possible

* clean as many issues as possible for Alerts.md

* clean up as much of ARP.md as possible

* clean up as much as possible for Bills.md

* make DeviceGroups.md as mdl happy as possible

* cleanup Devices.md

* make as mdl happy as possible Inventory.md and index.md

* mdl cleanup for Logs.md and PortGroups.md

* make Ports.md and Routing.md as happy as possible

* clean up Services.md, Switching.md, and Systems.md as much as possible

* more markup cleanup

* lots more md cleanup udner Devloping/

* reapply bits from #10343 that accidentally got removed when merging
2019-06-20 13:53:44 -05:00

994 B
Raw Blame History

source: Developing/Merging-Pull-Requests.md path: blob/master/doc/

Merging Pull Requests

GitHub

We will now build the monthly change log from our GitHub commits. When merging a commit, please ensure you:

  • Click the Merge pull request button
  • Give the merge a descriptive but short title
  • For the commit message prepend it with one of the following tags for the pull request to appear in the changelog:
    • devices: or newdevice: For new device support.
    • feature: or feat: To indicate this is a new or updated feature
    • webui: or web: To indicate this is an update to the WebUI
    • fix: or bugfix: To show this is a bug fix.
    • refactoring: or refactor: When the changes are refactoring a large portion of code
  • You can reference an issue number with #xyz, i.e #1234
  • Use the Confirm squash and merge button to merge.

Example commits

Feature

feature: Added new availability map #4401

New device

newdevice: Added support for Cisco ASA #4402