University-of-Basel-Studentprojects/Programmierprojekt
Archived
1
0
Fork 0
Code Issues 17 Pull Requests Actions Wiki Activity

External script to provide aid and enforce rules when creating issues or tasks #17

New Issue
Open
opened 2026-03-26 10:28:29 +01:00 by lars.winzer · 8 comments
lars.winzer commented 2026-03-26 10:28:29 +01:00 (Migrated from git.scicore.unibas.ch)
Copy Link
Copy Source

Feature Request

Summary

The new templates outlined in #16 require a lot of input. Sometimes inputs may be missed or not according to spec.

An external service can enforce these rules.

Required Workarround

Another member must actively enforce these rules, wasting time that could have been spent on other, more important tasks.

Discription of requested feature

An external program triggered via a GitLab webhook. It can respond to various events, such as a new issue, task, or merge request.

In the case of issues or tasks, several things can be checked.

  1. Is the issue or task assigned to a milestone? If not, the system should determine which milestone best fits the issue or task and then assign it accordingly.
  2. No additional labels have been added, or not all items on the checklist have been completed. The creator should be reminded to complete all items.

For all these notes or modifications, a comment should be added so that it is clear who made the change. In addition to the entry in the timeline.

GitLab offers excellent documentation on the Webhooks themselves and the possible list of triggers for these Webhooks.

Processing could be done via either a Python script with a webhook endpoint or n8n, which offers native GitLab integration.

### Feature Request ### Summary The new templates outlined in #16 require a lot of input. Sometimes inputs may be missed or not according to spec. An external service can enforce these rules. ### Required Workarround Another member must actively enforce these rules, wasting time that could have been spent on other, more important tasks. ### Discription of requested feature An external program triggered via a GitLab webhook. It can respond to various events, such as a new issue, task, or merge request. In the case of issues or tasks, several things can be checked. 1. Is the issue or task assigned to a milestone? If not, the system should determine which milestone best fits the issue or task and then assign it accordingly. 2. No additional labels have been added, or not all items on the checklist have been completed. The creator should be reminded to complete all items. For all these notes or modifications, a comment should be added so that it is clear who made the change. In addition to the entry in the timeline. GitLab offers excellent documentation on the [Webhooks](https://docs.gitlab.com/user/project/integrations/webhooks/) themselves and the possible list of [triggers](https://docs.gitlab.com/user/project/integrations/webhook_events/) for these Webhooks. Processing could be done via either a Python script with a webhook endpoint or n8n, which offers native GitLab integration.
lars.winzer commented 2026-03-26 10:29:04 +01:00 (Migrated from git.scicore.unibas.ch)
Copy Link
Copy Source

marked this issue as related to #16

marked this issue as related to #16
lars.winzer commented 2026-03-26 18:21:52 +01:00 (Migrated from git.scicore.unibas.ch)
Copy Link
Copy Source

mentioned in merge request !50

mentioned in merge request !50
lars.winzer commented 2026-03-26 18:23:19 +01:00 (Migrated from git.scicore.unibas.ch)
Copy Link
Copy Source

mentioned in commit 4b187fac27

mentioned in commit 4b187fac27461ea958f8254fd8a81e4d8a09599c
lars.winzer (Migrated from git.scicore.unibas.ch) closed this issue 2026-03-26 18:23:20 +01:00
lars.winzer (Migrated from git.scicore.unibas.ch) reopened this issue 2026-03-26 18:23:27 +01:00
lars.winzer commented 2026-03-26 18:23:53 +01:00 (Migrated from git.scicore.unibas.ch)
Copy Link
Copy Source

Specified wrong issue to be closed in https://git.scicore.unibas.ch/cs108-fs26/Gruppe-13/-/merge_requests/50

Specified wrong issue to be closed in https://git.scicore.unibas.ch/cs108-fs26/Gruppe-13/-/merge_requests/50
lars.winzer commented 2026-03-26 18:24:19 +01:00 (Migrated from git.scicore.unibas.ch)
Copy Link
Copy Source

mentioned in task #14

mentioned in task #14
lars.winzer commented 2026-03-28 13:18:09 +01:00 (Migrated from git.scicore.unibas.ch)
Copy Link
Copy Source

changed title from External script to provide aid an enforce rules when creating issues or tasks to External script to provide aid and enforce rules when creating issues or tasks

<p>changed title from <code class="idiff">External script to provide aid an enforce rules when creating issues or tasks</code> to <code class="idiff">External script to provide aid an<span class="idiff left right addition">d</span> enforce rules when creating issues or tasks</code></p>
lars.winzer commented 2026-04-07 20:18:43 +02:00 (Migrated from git.scicore.unibas.ch)
Copy Link
Copy Source

changed type from issue to task

changed type from issue to task
lars.winzer commented 2026-04-07 20:18:58 +02:00 (Migrated from git.scicore.unibas.ch)
Copy Link
Copy Source

Changed type from issue to task, as it is more suitable.

Changed type from issue to task, as it is more suitable.
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
achievement
Tasks related to milestone achievements
 bug
Issues related to programming errors on both client and server
 ci
Issues related to problems with the gitlab ci (incorrect or missing jobs)
 client
Issues (To-Dos and tasks) related to the client
 commands
Issues and tasks related to commands and thier infrastructure (CommandHandler, CommandParser, ...)
 documentation
Issues related to the documentation (for new or unclear, incorrect or incomplete entries)
 enhancement
Issues related to enhancements (also known as feature-requests)
 game-engine
Issues related to the game engine (incorrect state transitions or move validations)
 linting
Issues related to linting i.e. false detections, too generous linting, ...
 messages
Issues and tasks related to the messages and chats
 network
Issues and tasks related to the network (SessionReader / SessionWriter, Parser, ResponseBody, ...)
 outreach
Issues and tasks related to the outreach website and everything directly related to it
 server
Issues (To-Dos and tasks) related to the server
 task
Issues outlining and discussing a general task or implementation
 templates
Issues related to GitLab templates
 ui
Issues and tasks related to the client-side ui
 unit-test
Issues related to missing or already planned unit tests
 user
Issues and tasks related to the user management
No Label ci enhancement
Milestone
No items
No Milestone Milestone 4
Assignees
Clear assignees
lars-winzer (Lars Winzer)
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: University-of-Basel-Studentprojects/Programmierprojekt#17
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?