Closed iholder101 closed 1 year ago
This is only happened if two PRs are changing this file. otherwise, if this is the only change, then the sanity script knows to ignore this line.
This is done in hack/diff-csv.sh
that then used by both make sanity
and hack/build-manifests.sh
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
/close
@kubevirt-bot: Closing this issue.
Is this a BUG REPORT or FEATURE REQUEST?:
What happened: Since auto-generated files (e.g.
kubevirt-hyperconverged-operator.v1.9.0.clusterserviceversion.yaml
) contain creation dates, it means that whenever a new PR generates this file it always causes conflicts and demand rebasesFor example:
What you expected to happen: Reduce frequent need to rebase