| Age | Commit message (Collapse) | Author |
|---|
|
Adds links for writing commit messages and doing atomic commits.
|
|
based on the fact that we now only create release branches if they are actually necessary
|
|
so that the channel is clickable when posting the rules
This only applies to the `#get-support-here` channel as we don't want the mention of `#general` to be clickable to further reduce the chance of someone entering that channel for support as `#general` is not designed to give tech support.
|
|
As suggested by S2ymi
|
|
Adds a rule regarding the disallowing of alt accounts as is standard practice in most communities.
|
|
We are in fact not less strict than Discord ToS as we have to adhere to them ourselves as well as we are a public server.
|
|
GitBook seems to require links to be explicitly formatted as such to be clickable
|
|
The readme that was linked to was recently removed upstream resulting in a 404.
As Origin support in Lutris is being deprecated it makes no sense to keep linking to a page that is no longer up-to-date
|
|
that was lost when copy/pasting from Discord
Co-authored-by: amione <57235791+xamionex@users.noreply.github.com>
|
|
|
|
Adds a link which shows the history of the rules page on GitHub
|
|
https://taskinoz.com/northstar/ seems to occasionally either take too long to respond or falsely detect us as spam so easiest is to just skip it during linkcheck
|
|
The rules where committed under @xamionex's name as they were the last person to post them in the `#rules` channel and exact attribution is quite difficult at this time as the message is over two years old now.
Co-authored-by: amione <57235791+xamionex@users.noreply.github.com>
|
|
Current rules will be added in separate PR so that they can be properly attributed to their original author.
|
|
to match the structure in the sidebar and update any relative links
|
|
to facilitate adding more pages in the future
|
|
For the record, `~0x20000000` clears the 29th bit of the result from cpuid, while `0x20000000` replaces the result with one with just the 29th bit set (OPENSSL_ia32cap.3). The 29th bit represents the Intel SHA Extensions.
As such, if the second one (without the ~) works, the actual solution has nothing to do with the 29th bit; it's one of the others.
|
|
|
|
|
|
Previously only mentioned 10th and 11th gen Intel CPUs but since then 12th and 13th gen have also released.
|
|
v3 uses Node 16 which is slated for deprecation by GitHub Actions
|
|
Instead of posting messages in three separate channels, it's now one channel for everything
|
|
|
|
Embed ModdingDocs link instead of using an inline link
This is done is it renders nicer on GitBook itself.
|
|
|
|
|
|
Mention that mods can break campaign among other things.
|
|
|
|
Co-authored-by: Cyn <70904206+itscynxx@users.noreply.github.com>
|
|
Co-authored-by: Cyn <70904206+itscynxx@users.noreply.github.com>
|
|
Adds docs of how `ban`, `unban` and the `banlist.txt` work
|
|
|
|
|
|
|
|
|
|
When manually updating Northstar, core mods should still be deleted first.
This prevents issues in case a script file is removed in a Northstar update.
|
|
So that it's together with the other repository pages
|
|
Update directory to show browse local files
|
|
Adds a GitHub Action that auto-adds a label to a PR in case there are merge conflicts.
|
|
|
|
Moves out vanilla section to its own page and updates it to current changes in Northstar.
|
|
Adds section aimed at helpers, explaining how to help others in order to trouble shoot Northstar issues.
|
|
They seem to have uptime issues right now, causing our CI to fail.
|
|
|
|
`-vanilla` (#259)
`-vanilla` is replaced with `-nonorthstardll` and the description of `-vanilla` is updated.
|
|
Remove mention of waiting for launcher build to finish
No longer necessary as release build script now waits for launcher to
be done.
|
|
Remove mention of next-release branch from pull request template
`next-release` only existed while there were lots of changes still
happening to wiki as everything was new. Now that the dust has settled,
the preferred approach is to just hold of merging the change until the
release has been made.
Given our faster release cycle and fewer wiki changes this usually
doesn't incur any issues with merge conflicts caused by other changes
to wiki being merged.
|
|
There was two `handled`s, now there is one.
|
|
Adds PRs to the project board upon PR creation.
|
|
Co-authored-by: Cyn <70904206+itscynxx@users.noreply.github.com>
|
