I'm creating a Herald Rule for commits for a project. (I'm anticipating triggering the rule whenever a commit gets pushed to a repository that's tagged with that project or whenever a commit gets tagged with that project. Maybe that's not what it's intended for?) Even though I have permissions to edit the project, I end up not having permissions to edit the rule after I create it.
|phabricator||492fd29a1bd4d48dac1acdf3c89475d333af863b (Tue, Aug 30)|
|arcanist||10e5194752901959507223c01e0878e6b8312cc5 (Fri, Aug 26)|
|phutil||d6818e59c1764ede22cad56f8c5b1b527cb6a577 (Fri, Aug 26)|
Steps to reproduce:
- Create a project with the following:
- Set the Edit Policy to "Project Members".
- Add yourself as an initial member.
- Create a Herald Rule with the following:
- Create it for "Commits", "Commit Hook: Branches/Tags/Bookmarks", or "Commit Hook: Commit Content".
- Set the Rule Type to "Object".
- Set the Object to your newly created project.
- The Name, Conditions, and Action don't appear to affect the outcome. Set them to anything you like.
A new Herald Rule that you're allowed to edit?
A new Herald Rule that you can't edit.
You do not have permission to edit this object. Users with the "Can Edit" capability: * Project members can take this action. * Object rules inherit the edit policies of their objects.
If you change the project's Edit Policy to, say, yourself or "All Users", then you're able to edit the Herald rule.