Commit Graph

4 Commits

Author SHA1 Message Date
UdjinM6
a91eace041
chore/feat: few tweaks for "Check Potential Conflicts" action (#5330)
## Issue being fixed or feature implemented
small cleanups and improvements

## What was done?
pls see individual commits

## How Has This Been Tested?
see
https://github.com/dashpay/dash/actions/runs/4715728701/jobs/8362893373?pr=5330

## Breaking Changes
n/a

## Checklist:
- [x] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have added or updated relevant unit/integration/functional/e2e
tests
- [ ] I have made corresponding changes to the documentation
- [x] I have assigned this pull request to a milestone _(for repository
code-owners and collaborators only)_
2023-04-17 01:41:18 +03:00
PastaPastaPasta
f3cd4046c9
actions: introduce handle_potential_conflicts.py to only warn on true conflicts. Fail CI when there is a conflict (#4655)
* introduce handle_potential_conflicts.py to only warn on true conflicts. Fail CI when there is a conflict

Signed-off-by: Pasta <pasta@dashboost.org>

* remove unneeded input assign

Co-authored-by: UdjinM6 <UdjinM6@users.noreply.github.com>

* use dashpay instead of PastaPastaPasta

Signed-off-by: Pasta <pasta@dashboost.org>

* Update .github/workflows/handle_potential_conflicts.py

Co-authored-by: UdjinM6 <UdjinM6@users.noreply.github.com>

* more linter fixes

Co-authored-by: UdjinM6 <UdjinM6@users.noreply.github.com>
2022-01-13 17:26:47 +03:00
PastaPastaPasta
1c925ed3d2
actions: use pull_request_target instead of pull_request, use custom fork (#4647)
* use pull_request_target instead of pull_request

Signed-off-by: Pasta <pasta@dashboost.org>

* use pasta based action 0.1.1

Signed-off-by: Pasta <pasta@dashboost.org>
2021-12-30 22:04:14 +03:00
PastaPastaPasta
58b2605808
actions: implement predict-conflicts actions (#4645)
* add predict-conflicts.yml

* remove commented out permission
2021-12-30 19:32:11 +03:00