I conceptually like the approach you outline for --only-new.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Nov 9 2015
I was thinking of changing arc lint --only-new to do the following:
You may also be interested in T9212 which explains a bit better why "free support" is increasing burdensome for the upstream.
More specifically we'd prefer if people:
We prefer people follow our posted guidelines on filing feature requests. We don't take feature requests that don't state a problem. Specifically "feature does not exist" does not satisfy our criteria for requesting features.
Sorry, I don't understand, why you closed this. The problem is:
- You can block commits, for example, if you don't want to see private data there
- But if you want to block private data, you need to put in that data in a global herald rule, which is public visible
- But if you don't use regex, you can block private data, yes, but everyone who can access herald, can see the data, so this feature is not very useful at the moment.
- But if you want to block private data, you need to put in that data in a global herald rule, which is public visible
Works for me!
There won't be any configuration for comments.
For reference, I think this is an excellent plan and I'm stoked to see internal comments being considered. (If I already have to get my users to sign up for a Phabricator account, it's good if they don't have to also log into Disqus.)
#iwin
Sniped!
Please see:
Reproduction steps must be included with all bug reports. Thanks!
I'm starting to think Phurl is something entirely different than what I'm thinking of... Yup. Nevermind me then.
Used
./bin/config set phurl.short-uri http://p/
So I just tested this out, against: http://p/ and all I'm getting is a 404 page. Does it need to have a TLD?
I'll yank it in one diff, so it's easy to resurrect.
I could see some future where you maybe want a split blog view (employees can comment privately, public comments publicly), but it's also hard for me to envision large corporation trusting Phabricator over Wordpress is they have super serious needs.
Yeah, I'm onboard with that plan.
I've managed to reproduce the issue on Ubuntu 15.10
(This is just a note for me to make sure I don't forget about it, I'll follow up here before we unprototype.)
My plan is to get all the "clean up" done, then re-design the landing page and the blog page. It's definitely not easy to get around or discover anything.
Are you planning a fully specifiable merge command so we can run anything we want for merging?
All the policy, merge strategy, etc., stuff is hard-coded to the easiest set of reasonable defaults. Some of these defaults may not be suitable for many installs (e.g., always rebase, always merge to master, require edit capability for imported repositories in order to perform merges). I expect to expand these shortly, I just don't want to focus on making things more flexible until they actually work.
To be precise webserver had not correct permission.
I solved
$ sudo chcon -R --type=httpd_sys_rw_content_t phabricator/
$ sudo chcon -R --type=httpd_sys_rw_content_t libphutil/
$ sudo chcon -R --type=httpd_sys_rw_content_t arcanist/
Excellent; that's good to know. Thanks!
running arc diff --update with an accidentally incorrect revision ID would be less likely to succeed if revisions were only editable by their author
Are these updates legitimately accidental? Can you explain how users are accidentally making updates to others' revisions? I don't think we've seen this behavior on this install, or heard about it from other installs.
I suspect T9132 will address this use case.
This was fixed as part of T9657:
accidentally updating revisions that aren't theirs
Sounds like webserver / php / something wasn't installed correctly.
I put the prefix you wanted on "Open"
Who is hosting the repository, Phabricator or an external source? Rough Googling suggests the repository might be corrupt or the disk might be full.
What's the actual error you've encountered when trying to add such a file?
I will try your config at the afternoon, at the moment I can not access my git. You used only suffixes, so I will try it with your config, maybe that was my fault.
Index _status in 2.0 replaced _stats https://www.elastic.co/guide/en/elasticsearch/reference/2.0/indices-status.html
Nov 8 2015
Maybe there can be a way to enable it as a menu item, but being disabled by default. Your call! Thanks for getting back to me despite the beta label (forgot that you don't take bug reports / features on it yet).
Only the most common actions are there, otherwise we'd have over 50 items. Personal customization offers better flexibility to individual workflows.
In our community, for regular members (not involved in board/admin tasks), I expect it to be the one most commonly used action (the other common action being commenting on other people's posts). Either way, I can work with providing a separate link in a dashboard box. However, for a global menu I would find it confusing to not find "Create" actions in the "Create New" menu.
How often do you expect everyone to write a blog post? Mostly this will just clutter the quick create menu. We expect T8994 to cover these edge cases.
- I cherry-picked this to stable (rP111c48b2).
- I deployed this fix to the Phacility cluster.