.gitignore: Only ignore sydent.conf and sydent.db if they occur in th… #354
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…e project's base folder.
Reasoning: In Debian, we provide a debian/sydent.conf file as the
initial config template file to be installed to /etc/matrix-sydent/.
This file is stored in the Debian packaging Git (available on
https://salsa.debian.org/matrix-team/matrix-sydent/).
With this change in upstream's .gitignore file, we make sure that
changes in debian/sydent.conf get properly tracked via the packaging
Git, whereas changes to sydent.conf (in the project's basedir) are hidden
from Git (which is relevant for software testing by upstream).
The same logic quasi applies to the sydent.db file, although the Debian
package, of course, does not ship such a file.
Signed-off-by: Mike Gabriel mike.gabriel@das-netzwerkteam.de
Pull Request Checklist
EventStore
toEventWorkerStore
.".code blocks
.