| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
class method DYNAMIC_COLUMNS
When working on bug 1253535 I kept encountering the fragility of our model system.
This fragility involves two things:
1) Extensions adding new columns to model objects
2) The use of those model objects in checksetup.
In particular, the SecureMail extension causes this problem because (at checksetup-time) we need to lookup certain Group objects.
Thus I propose to
1) allow model classes to take their list of columns from the informations schema (exposed via `bz_table_columns_real`)
2) Have Bugzilla::Group do this when being used in a commandline (e.g. checksetup) context.
|
|
the revision with the project
|
|
author
|
|
instead of PhabricatorProjectsPolicyRule
|
|
|
|
|
|
|
|
|
|
|
|
large file before uploading it
|
|
|
|
proper label
|
|
product selector on Browse and Enter Bug pages
|
|
Browse page
|
|
|
|
|
|
/bug/ALIAS.
|
|
|
|
by the bmo-editbugs-team project (editbugs)
|
|
extension
|
|
|
|
|
|
Phabricator and not from BMO
|
|
|
|
|
|
|
|
|
|
on revisions without a bug id associated
|
|
|
|
|
|
|
|
|
|
|
|
initial revision email after BMO has updated the policies
|
|
|
|
|
|
$self->type()
|
|
|
|
get_phab_bmo_ids() which is no longer part of the code
|
|
|
|
|
|
|
|
Phabricator, it should fix permissions
|
|
|
|
better type checking
|
|
still blocking reviewers
|
|
module for better type checking"
This reverts commit 739676cf4b122cdec12981c2bc3a79c3f54aa7e4.
|
|
better type checking
|
|
user already has a flag set even if flag is status of ?
|
