5436-mensajeClienteSinCorreo #1469
Member
No description provided.
CR / Tests passed
label
carlossa
added 3 commits 2023-04-20 09:34:00 +00:00
gitea/salix/pipeline/head This commit looks good
Details
gitea/salix/pipeline/head There was a failure building this commit
Details
carlossa
scheduled this pull request to auto merge when all checks succeed 2023-04-20 13:24:08 +00:00
carlossa
added 1 commit 2023-04-20 13:24:22 +00:00
gitea/salix/pipeline/head There was a failure building this commit
Details
carlossa
canceled auto merging this pull request when all checks succeed 2023-04-21 07:19:20 +00:00
alexm
added 1 commit 2023-04-24 06:02:04 +00:00
gitea/salix/pipeline/head There was a failure building this commit
Details
carlossa
added 1 commit 2023-04-24 08:38:11 +00:00
gitea/salix/pipeline/head This commit looks good
Details
carlossa
added 1 commit 2023-04-24 12:41:02 +00:00
gitea/salix/pipeline/head This commit looks good
Details
Merge pull request '5436-mensajeClienteSinCorreo' (!1469) from 5436-mensajeClienteSinCorreo into dev
No reviewers
Labels
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: verdnatura/salix#1469
Loading…
Reference in New Issue
No description provided.
Delete Branch "5436-mensajeClienteSinCorreo"
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?