`rules:changes` doesn't work as expected

[martijnbastiaan]

The CI job debian-bindist is only supposed to trigger when files relevant to it change:

clash-compiler/.ci/gitlab/publish.yml

Lines 27 to 52 in 250aea4

	# Run every night, when explicitly triggered, or when tagged (release)
	.run-on-nightly-and-changes:
	rules:
	- if: $CI_PIPELINE_SOURCE == "schedule"
	- if: $CI_PIPELINE_SOURCE == "trigger"
	- if: '$CI_COMMIT_TAG != null' # tags
	- if: '$CI_COMMIT_TAG == null'
	changes:
	- .gitlab.yml
	- .ci/**/*
	- .ci/*
	- ./*/*.cabal
	# Create Debian packages.
	debian-bindist:
	extends: .run-on-nightly-and-changes
	needs: []
	image: docker.pkg.github.com/clash-lang/clash-compiler/bindist-debian-focal:2020-11-20
	stage: pack
	artifacts:
	when: always
	paths:
	- .ci/bindist/linux/debian/focal/build
	expire_in: 1 week
	script:
	- .ci/bindist/linux/debian/scripts/build.sh focal

This only seems to work every once in a while though. For example, #1660 doesn't change any of the files mentioned, but it did trigger debian-bindist.

This is either a bug in our config file, or an upstream bug.

[martijnbastiaan]

The problems seems to be that force pushes run without context. GitLab CI defaults to the "safe" behavior of executing the test.