senaduka/old-riskletpy
1
0
Fork 0
Code Issues 5 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Update sections related to risks after man change of risks #117

Open
amirsabani303 wants to merge 1 commits from update-content-after-risk-update into master
pull from: update-content-after-risk-update
merge into: senaduka:master
Conversation 0 Commits 1 Files Changed 2 +55 -3
amirsabani303 commented 2025-10-09 19:43:17 +02:00 (Migrated from gitlab.com)
Copy Link

Dodat je update content button, nakon sto se manuelno selektuju rizici, da bi controle i explanations bile sa poslednjim informacijama.

Dodat je update content button, nakon sto se manuelno selektuju rizici, da bi controle i explanations bile sa poslednjim informacijama.
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin update-content-after-risk-update:update-content-after-risk-update
git checkout update-content-after-risk-update
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
senaduka
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: senaduka/old-riskletpy#117
Delete Branch "update-content-after-risk-update"

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?