Replace Travis with GitHub actions and fix many typos (#1657)

* Create django.yml

* Fix working directory

* ..

* .

* ..

* a.

* ..

* .

* Fix typo

* Install hunspell

* maxfail

* Fix install

* .

* Reduce number of typos

* Even less typos

* Postgres debug

* Spelling fixes, yet again

* Postgres with PW

* Fix failing test

* New workflows

* Fix syntax error

* Install gettext

* Test aginst python 3.6 as well

* Clean up strategies

* Add badge, do not ignore migrations

* Use pip cache
This commit is contained in:
Raphael Michel
2020-04-22 12:07:58 +02:00
committed by GitHub
parent 27d6e49c4a
commit d224b5387d
68 changed files with 1377 additions and 973 deletions

View File

@@ -58,7 +58,7 @@
<div class="col-sm-12 col-md-9 nomargin-bottom">
{% blocktrans trimmed %}
You can remove personal data such as names and email addresses from your event and only retain the
finanical information such as the number and type of ticekts sold.
financial information such as the number and type of tickets sold.
{% endblocktrans %}
</div>
<div class="col-sm-12 col-md-3">

View File

@@ -68,7 +68,7 @@
{% csrf_token %}
<input type="hidden" name="testmode" value="false">
<p>
{% trans "Your shop is currently in test mode. All orders are not persistant and can be deleted at any point." %}
{% trans "Your shop is currently in test mode. All orders are not persistent and can be deleted at any point." %}
</p>
<div class="form-inline">
<label class="checkbox">

View File

@@ -8,7 +8,7 @@
To make your products actually available, you also need quotas. Quotas define, how many instances of
your product pretix will sell. This way, you can configure whether your event can take an unlimited
number of attendees or the number of attendees is limited. You can assign a product to multiple quotas
to fulfil more complex requirements, e.g. if you want to limit the total number of tickets sold and the
to fulfill more complex requirements, e.g. if you want to limit the total number of tickets sold and the
number of a specific ticket type at the same time.
{% endblocktrans %}
</p>

View File

@@ -20,7 +20,7 @@
{% csrf_token %}
<p>
{% blocktrans trimmed with amount=refund.amount|money:request.event.currency method=refund.payment_provider.verbose_name pending=pending_sum|money:request.event.currency total=order.total|money:request.event.currency %}
We recevied notice that <strong>{{ amount }}</strong> have been refunded via
We received notice that <strong>{{ amount }}</strong> have been refunded via
<strong>{{ method }}</strong>. If this refund is processed, the order will be underpaid by
<strong>{{ pending }}</strong>. The order total is <strong>{{ total }}</strong>.
{% endblocktrans %}

View File

@@ -50,7 +50,7 @@
<div class="alert alert-info" data-display-dependency="#id_refund_as_giftcard">
{% blocktrans trimmed %}
Since you are refunding your customers orders to gift cards, you should explain to them how to
access their giftcards. The easiest way to do this, is to include an explanation and a link to
access their gift cards. The easiest way to do this, is to include an explanation and a link to
their order using the here provided email functionality.
{% endblocktrans %}
</div>

View File

@@ -207,7 +207,7 @@
</div>
<div class="row control-group pdf-info">
<div class="col-sm-12">
<label>{% trans "Prefered language" %}</label><br>
<label>{% trans "Preferred language" %}</label><br>
<select class="form-control" id="pdf-info-locale">
<option value="">{% trans "Order locale" %}</option>
{% for l in locales %}

View File

@@ -14,7 +14,7 @@
<legend>{% trans "Step 1: Download data" %}</legend>
<p>
{% blocktrans trimmed %}
You are about to permamanently delete data from the server, even though you might be required to
You are about to permanently delete data from the server, even though you might be required to
keep
some of this data on file. You should therefore download the following file and store it in a safe
place: