Go to file
giles 8d38989ff4
push / format (push) Successful in 53s Details
target / format (pull_request) Successful in 58s Details
push / document (push) Successful in 1m46s Details
target / document (pull_request) Successful in 1m49s Details
push / schema (push) Successful in 26s Details
target / schema (pull_request) Successful in 30s Details
target / review (pull_request) Successful in 28s Details
documented
2023-11-23 00:21:46 +00:00
.github .. 2023-11-22 22:51:13 +00:00
displays Update displays/legacy-mimics-ta521_mimic.xml 2023-11-22 21:37:04 +00:00
document documented 2023-11-20 21:21:22 +00:00
ft-view-screens documented 2023-11-23 00:21:46 +00:00
global objects Update global objects/cfg.xml 2023-11-23 00:19:44 +00:00
instructions initial-commit 2023-11-20 21:08:07 +00:00
plc initial-commit 2023-11-20 21:08:07 +00:00
recipes ... 2023-11-20 21:20:05 +00:00
.gitignore initial-commit 2023-11-20 21:08:07 +00:00
README.md initial-commit 2023-11-20 21:08:07 +00:00
equipment-model.axml initial-commit 2023-11-20 21:08:07 +00:00
equipment-model.json ... 2023-11-20 21:15:51 +00:00
servers.yml initial-commit 2023-11-20 21:08:07 +00:00

README.md

batch-example

This repository will store, format, document and allow versioning and approval of a batch configuration.

This repository only contains exported configuration. It does not contain any binary files (eg equipment-model.cfg nor system state or log files). These are excluded using the .gitignore file.

suggested teams

configured at organisation

  • Owners
  • reviewers
  • reviewers-2
  • ci-bots

suggested branch protection

protect branch main

  • disable push
  • protected file patterns - .github/**
  • require 2 approvals
  • restrict approvals to reviewers and reviewers-2 teams
  • dismiss state approvals
  • enable status check for **
  • enable merge whitelist to owners
  • block merge on rejected reviews
  • block merge on official review requests
  • block merge if pull request is outdated

protect branch **

  • protected file patterns - .github/**

you will need to:

give a bot user (eg batch-bot) write access and make them members of ci-bots team

generate a new token for this user https://sigyl.com/git/user/settings/applications with

  • write:issue
  • write:repository
  • read:user

set an action secret called BOT_TOKEN to it