Page MenuHomePhabricator

New revisions aren't always assigned an Arcanist Project automatically
Closed, WontfixPublic

Description

When creating a new arcanist ad-hoc project (by setting up .arcconfig in a repository and setting a project.name or the old project_id), the entry would be listed under the now deprecated Repositories app, but the revision will set no Arcanist Project.

However, going to the Repositories app and manually associating the newly created Arcanist Project to a Repository does fix the issue. This should be done automatically, especially considering that the revision DOES automatically show the proper Repository.

This is probably just another step in the deprecation of the Repository app, but still, currently an issue that affects how fields are populated and treated.

Related Objects

Event Timeline

jsotuyod raised the priority of this task from to Needs Triage.
jsotuyod updated the task description. (Show Details)
jsotuyod added a project: Arcanist.
jsotuyod added a subscriber: jsotuyod.

Do you mean .arcconfig, or are you trying to set it in .arclint?

Sorry, you are right, editting

chad renamed this task from New revisions aren't always assigned an Arcanist Project automaticallly to New revisions aren't always assigned an Arcanist Project automatically.Oct 3 2014, 3:52 AM
chad triaged this task as Wishlist priority.