features rebuild with no change is not clean

[YesCT]

I followed the readme and set up a vagrant machine. I made a view, and then did
drush fb -y

but I got unrelated changes.

So I destroyed the machine, removed the git repo and reinstalled everything from scratch.

Should we commit something cleaner? Or let unrelated changes get committed in other issues?

[thejimbirch]

Cathy,

Since you are working with the live database here, you are most likely
committing other admins UI changes.

To see the changes, you can:

git diff path/to/file

If you do not want to commit other people's work, you can only add and
commit your changes, which I believe would be the views feature in this
case.

Jim
On Mon, Jan 11, 2016 at 5:53 PM Cathy Theys [email protected]
wrote:

I followed the readme and set up a vagrant machine I made a view, and then
did
drush fb -y

but I got unrelated changes

So I destroyed the machine, removed the git repo and reinstalled
everything from scratch

Should we commit something cleaner? Or let unrelated changes get committed
in other issues?

—
Reply to this email directly or view it on GitHub
#12.

[bt-eric]

There are a few issues I've noticed with features. I would point my finger at features more than features builder. In any event, here is what I see when drush fb -y:

• Disabled views are getting exported as enabled.
• View fields for logo and avatar seem to interchange.
• Organic Groups adds an og_user_node field to the user, and somehow features makes og think it needs to add this field again. Seeing og_user_node already exists it creates an og_user_node1, og_user_node2, etc.