Hey, I wanted to ask you how do you work with .gitignore on your fork of backdrop: .gitignore includes an entry for it self, but as it is already tracked, any local changes to the file will be pushed to my fork and added to the eventual PR I made for the upstream. So I need to untrack it.
git rm --cached .gitignore indeed untracks locally the file, but it also deletes the file in my fork repo and would delete it in a PR.
Thus, how do you do to change your local .gitignore without pushing its changes?
Thanks!!
Recent comments
The issue was merely caused by Varnish, enabled by adding an enable_varnish file. After I removed that file, the forms started to work again.
Submitted form values are no longer saved
Do I need to delete some values from the database, for example from the cache_form table? I forgot Backdrop core does not use that database table, differently from Drupal 7....
Submitted form values are no longer saved
I would love for the people at the meeting to go back to my PRs for bug and feature issues that are languishing in the issue queue. These were discussed last month, and have fallen off the radar...
Oct 24th Weekly Meetings
Thank you for clarifications. I just checked my profile and now all are 'disabled' as well. Apparently there is a lag of about 24 hours between Forum Topics and Profile Email.
Profile problems
I agree that in theory, these repos should be available for a long time. BUT, I also agree that we should not risk it. It would be a huge loss to our community if these repos disappeared....
Initiative Proposal: Drupal 7 MIRROR