| Age | Commit message (Collapse) | Author |
|---|
|
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>
|
|
|
|
fix: Add Manjaro forum link to ignore list
Manjaro forums are down and I don't want our CI to fail because of that
|
|
Co-authored-by: NoCatt <86153630+NoCatt@users.noreply.github.com>
|
|
Co-authored-by: Cyn <70904206+itscynxx@users.noreply.github.com>
|
|
Still empty for now
Co-authored-by: NoCatt <86153630+NoCatt@users.noreply.github.com>
|
|
Adds basic debugging documentation for Visual Studio and x64dbg
|
|
Checks whether any links in markdown files in a push or pull request are broken.
|
|
|
|
|
|
|
|
Automatically adds all opened issues to the project board.
|
|
This is a rough outline without specific detail.
The process always changes too so this page will likely need constant
updating to avoid turning stale.
|
|
|
|
* Adjust development section folder structure
The structure of development related pages is a leftover from when
modding and development were combined in a single folder.
Modding related content has since long moved to ModdingDocs.
As such we should update the folder structure accordingly
* Update broken links
|
|
So that link checking tools don't see it as potential incomplete
hyperlink
|
