Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(linux): sync PKGBUILD with pacman-repo #2833

Merged
merged 1 commit into from
Jul 12, 2024

Conversation

ReenigneArcher
Copy link
Member

Description

  • Update PKGBUILD in pacman-repo, via a PR, when we create a stable release
  • A few updates to the PKGBUILD to make it more inline with the pacman-repo and easier to sed
  • A few updates to the archlinux dockerfile

Screenshot

Issues Fixed or Closed

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Dependency update (updates to dependencies)
  • Documentation update (changes to documentation)
  • Repository update (changes to repository files, e.g. .github/...)

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

  • I want maintainers to keep my branch updated

@ReenigneArcher ReenigneArcher force-pushed the build(linux)-sync-PKGBUILD-with-pacman-repo branch from 21327e9 to c29ac95 Compare July 11, 2024 15:01
Copy link

codecov bot commented Jul 11, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 9.04%. Comparing base (6607a28) to head (0e8a7be).
Report is 2 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##           master   #2833      +/-   ##
=========================================
+ Coverage    8.99%   9.04%   +0.05%     
=========================================
  Files          95      96       +1     
  Lines       17312   17437     +125     
  Branches     8236    8276      +40     
=========================================
+ Hits         1557    1578      +21     
- Misses      12890   12972      +82     
- Partials     2865    2887      +22     
Flag Coverage Δ
Linux 6.80% <ø> (-0.01%) ⬇️
Windows 4.25% <ø> (+0.09%) ⬆️
macOS-12 10.06% <ø> (-0.04%) ⬇️
macOS-13 9.97% <ø> (-0.04%) ⬇️
macOS-14 10.29% <ø> (-0.02%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 2 files with indirect coverage changes

@ReenigneArcher ReenigneArcher force-pushed the build(linux)-sync-PKGBUILD-with-pacman-repo branch 8 times, most recently from 6014dba to 3aaef13 Compare July 12, 2024 17:10
@ReenigneArcher ReenigneArcher force-pushed the build(linux)-sync-PKGBUILD-with-pacman-repo branch from 3aaef13 to 0e8a7be Compare July 12, 2024 17:11
@ReenigneArcher ReenigneArcher marked this pull request as ready for review July 12, 2024 17:15
@ReenigneArcher ReenigneArcher enabled auto-merge (squash) July 12, 2024 17:15
@ReenigneArcher ReenigneArcher merged commit f3a164e into master Jul 12, 2024
49 checks passed
@ReenigneArcher ReenigneArcher deleted the build(linux)-sync-PKGBUILD-with-pacman-repo branch July 12, 2024 17:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant