SHA256

Files

Adam Majer 8db558891a direct: remove config.Branch clobbering

use our own copy of branch instead of writing it in the config.
This should fix handling of default branches where the default
branch differs between repositories.

2025-11-04 18:00:21 +01:00

.gitignore

rename things

2024-09-13 14:58:10 +02:00

example.json

Migrate to prjgit based config

2025-03-23 16:33:06 +01:00

links_test.go

wip

2025-03-13 08:46:21 +01:00

links.go

push changes if link changed

2025-03-16 20:29:42 +01:00

main.go

direct: remove config.Branch clobbering

2025-11-04 18:00:21 +01:00

README.md

update READMEs for workflow bots

2025-08-25 11:32:51 +02:00

README.md

Direct Workflow bot

Areas of responsibility

Keep ProjectGit in sync with packages in the organization
- on pushes to package, updates the submodule commit id to the default branch HEAD (as configured in Gitea)
- on repository adds, creates a new submodule (if non empty)
- on repository removal, removes the submodule

NOTE: reverts (push HEAD^) are not supported as they would step-on the work of the workflow-pr bot. Manual update of the project git is required in this case.

Configuration

Uses workflow.config for configuration. Parameters

Workflows: ["direct"] -- direct entry enables direct workflow. Mandatory
Organization: organization that holds all the packages. Mandatory
Branch: branch updated in repo's, or blank for default package branch
GitProjectName: package in above org, or org/package#branch for PrjGit. By default assumes _ObsPrj with default branch and in the Organization

NOTE: -rm, -removed, -deleted are all removed suffixes used to indicate current branch is a placeholder for previously existing package. These branches will be ignored by the bot, and if default, the package will be removed and will not be added to the project.

Target Usage

Devel project, where direct pushes to package git are possible