When project filtering and enhanced commits are active, for example
public $enforce_explicit_limits = true;
public $permitted_projects = array(
"jira-projects/FKAMP",
"jira-projects/MISC",
"jira-projects/ADBLK",
"jira-projects/HLS",
"misc/docker-gitphp",
"websites/Gitlab-Issue-Listing-Script",
"websites/privacy-sensitive-analytics",
"websites/videos.bentasker.co.uk"
);
public $enhanced_commit_notifications = true;
Issue pages may break if they contain a commit notification from a project not included in $permitted_projects
.
#30 | Show enhanced commit information in issue pages |
Activity
23-Apr-22 09:37
assigned to @btasker
23-Apr-22 09:39
In hindsight, this was an obvious outcome...
When enhanced commit notifications are active, for each commit notification we detect we call
getCommit()
However, like most other methods, that applies project filters
Which results in our page being killed
23-Apr-22 09:42
We can add a variable to the signature that allows us to disable that check, but we'll then fail at a later stage (as
getCommit()
callsgetProject()
) so we need to pass that on through23-Apr-22 09:47
mentioned in commit f10dd163620f519494ff17f674c77af154034f4b
Message
Add internal variable $enforce_filters for websites/Gitlab-Issue-Listing-Script#37
This allows us to conditionally turn off project filtering when necessary - for example, to ensure that we can still display enhanced commit notifications even if the referencing commit isn't in a project in the permitted list
23-Apr-22 10:10
marked this issue as related to #30