summaryrefslogtreecommitdiffhomepage
AgeCommit message (Collapse)Author
2023-11-07Fix mouse/touch/gestures for PLATFORM_DRM (#3515)ubkp
2023-11-07Update m3d.hRay
2023-11-07Update cgltf.hRay
2023-11-07Updated dr audio librariesRay
2023-11-07Update miniaudio.hRay
2023-11-07Add ES 3.0 to CMakeOptions (#3514)mooff
2023-11-06Fix warnings in visual studio (#3512)Jeffery Myers
2023-11-06Update raygui.hRay
2023-11-06Merge branch 'master' of https://github.com/raysan5/raylibRay
2023-11-06Update codeql.ymlRay
2023-11-06Update codeql.ymlRay
2023-11-06REVIEWED: `CodeQL` workflow, cleaning and organizationRay
2023-11-06REVIEWED: `sinfl` external library to avoid ASAN complaints #3349Ray
2023-11-06REVIEWED: `ScanDirectoryFiles*()`- Paths building slashes sides #3507Ray
2023-11-06Add CodeQL Workflow for Code Security Analysis (#3476)b4yuan
* Add CodeQL Workflow for Code Security Analysis Add CodeQL Workflow for Code Security Analysis This pull request introduces a CodeQL workflow to enhance the security analysis of our repository. CodeQL is a powerful static analysis tool that helps identify and mitigate security vulnerabilities in our codebase. By integrating this workflow into our GitHub Actions, we can proactively identify and address potential issues before they become security threats. We added a new CodeQL workflow file (.github/workflows/codeql.yml) that - Runs on every push and pull request to the main branch. - Excludes queries with a high false positive rate or low-severity findings. - Does not display results for third-party code, focusing only on our own codebase. Testing: To validate the functionality of this workflow, we have run several test scans on the codebase and reviewed the results. The workflow successfully compiles the project, identifies issues, and provides actionable insights while reducing noise by excluding certain queries and third-party code. Deployment: Once this pull request is merged, the CodeQL workflow will be active and automatically run on every push and pull request to the main branch. To view the results of these code scans, please follow these steps: 1. Under the repository name, click on the Security tab. 2. In the left sidebar, click Code scanning alerts. Additional Information: - You can further customize the workflow to adapt to your specific needs by modifying the workflow file. - For more information on CodeQL and how to interpret its results, refer to the GitHub documentation and the CodeQL documentation. Signed-off-by: Brian <[email protected]> * Add CodeQL Workflow for Code Security Analysis Add CodeQL Workflow for Code Security Analysis This pull request introduces a CodeQL workflow to enhance the security analysis of our repository. CodeQL is a powerful static analysis tool that helps identify and mitigate security vulnerabilities in our codebase. By integrating this workflow into our GitHub Actions, we can proactively identify and address potential issues before they become security threats. We added a new CodeQL workflow file (.github/workflows/codeql.yml) that - Runs on every pull request (functionality to run on every push to main branches is included as a comment for convenience). - Runs daily. - Excludes queries with a high false positive rate or low-severity findings. - Does not display results for git submodules, focusing only on our own codebase. Testing: To validate the functionality of this workflow, we have run several test scans on the codebase and reviewed the results. The workflow successfully compiles the project, identifies issues, and provides actionable insights while reducing noise by excluding certain queries and third-party code. Deployment: Once this pull request is merged, the CodeQL workflow will be active and automatically run on every push and pull request to the main branch. To view the results of these code scans, please follow these steps: 1. Under the repository name, click on the Security tab. 2. In the left sidebar, click Code scanning alerts. Additional Information: - You can further customize the workflow to adapt to your specific needs by modifying the workflow file. - For more information on CodeQL and how to interpret its results, refer to the GitHub documentation and the CodeQL documentation (https://codeql.github.com/ and https://codeql.github.com/docs/). Signed-off-by: Brian <[email protected]> * Add CodeQL Workflow for Code Security Analysis Add CodeQL Workflow for Code Security Analysis This pull request introduces a CodeQL workflow to enhance the security analysis of our repository. CodeQL is a powerful static analysis tool that helps identify and mitigate security vulnerabilities in our codebase. By integrating this workflow into our GitHub Actions, we can proactively identify and address potential issues before they become security threats. We added a new CodeQL workflow file (.github/workflows/codeql.yml) that - Runs on every pull request (functionality to run on every push to main branches is included as a comment for convenience). - Runs daily. - Excludes queries with a high false positive rate or low-severity findings. - Does not display results for git submodules, focusing only on our own codebase. Testing: To validate the functionality of this workflow, we have run several test scans on the codebase and reviewed the results. The workflow successfully compiles the project, identifies issues, and provides actionable insights while reducing noise by excluding certain queries and third-party code. Deployment: Once this pull request is merged, the CodeQL workflow will be active and automatically run on every push and pull request to the main branch. To view the results of these code scans, please follow these steps: 1. Under the repository name, click on the Security tab. 2. In the left sidebar, click Code scanning alerts. Additional Information: - You can further customize the workflow to adapt to your specific needs by modifying the workflow file. - For more information on CodeQL and how to interpret its results, refer to the GitHub documentation and the CodeQL documentation (https://codeql.github.com/ and https://codeql.github.com/docs/). Signed-off-by: Brian <[email protected]> * Add CodeQL Workflow for Code Security Analysis Add CodeQL Workflow for Code Security Analysis This pull request introduces a CodeQL workflow to enhance the security analysis of our repository. CodeQL is a powerful static analysis tool that helps identify and mitigate security vulnerabilities in our codebase. By integrating this workflow into our GitHub Actions, we can proactively identify and address potential issues before they become security threats. We added a new CodeQL workflow file (.github/workflows/codeql.yml) that - Runs on every pull request (functionality to run on every push to main branches is included as a comment for convenience). - Runs daily. - Excludes queries with a high false positive rate or low-severity findings. - Does not display results for git submodules, focusing only on our own codebase. Testing: To validate the functionality of this workflow, we have run several test scans on the codebase and reviewed the results. The workflow successfully compiles the project, identifies issues, and provides actionable insights while reducing noise by excluding certain queries and third-party code. Deployment: Once this pull request is merged, the CodeQL workflow will be active and automatically run on every push and pull request to the main branch. To view the results of these code scans, please follow these steps: 1. Under the repository name, click on the Security tab. 2. In the left sidebar, click Code scanning alerts. Additional Information: - You can further customize the workflow to adapt to your specific needs by modifying the workflow file. - For more information on CodeQL and how to interpret its results, refer to the GitHub documentation and the CodeQL documentation (https://codeql.github.com/ and https://codeql.github.com/docs/). Signed-off-by: Brian <[email protected]> * Run CodeQL Analysis weekly + incorporate build script into WF * remove: fail_on_error.py * update: codeql.yml --------- Signed-off-by: Brian <[email protected]>
2023-11-06REVIEWED: Scissor mode to support RenderTexture #3510Ray
2023-11-06BeginScissorMode checks for render texture to avoid using GetWindowScaleDPI ↵gulrak
(#3510)
2023-11-06ADDED: Flag to know we are rendering to texture #3510Ray
2023-11-06[build]: add uninstall cmake target (#3511)Aniket Teredesai
2023-11-05Merge branch 'master' of https://github.com/raysan5/raylibRay
2023-11-05REVIEWED: `rlgl_standalone` examples #3487Ray
Example is intended for `PLATFORM_DESKTOP` only and OpenGL 3.3 Core profile.
2023-11-05Updated GLFW for 64bitRay
2023-11-05Update README.mdRay
2023-11-05Update Makefile (#3509)JupiterRider
2023-11-05Update qoa.hRay
2023-11-05Update rl_gputex.hRay
2023-11-05Update qoi.hRay
2023-11-05Update README.mdRay
2023-11-05Jaylib is now up-to-date (#3508)glowiak
2023-11-05Updated open graph for examplesRay
2023-11-05Updating web shells open-graph infoRay
2023-11-04Allow raylib to be built with zig 0.11.0 and zig 0.12.0dev (master) (#3506)freakmangd
* allow zig 0.11.0 and 0.12.0dev to build raylib * update comment
2023-11-03Update rcore.cRay
2023-11-03ADDED: `LoadRandomSequence()`/`UnloadRandomSequence()`Ray
2023-11-03Fixed Issue 3504 (#3505)AndreaBoroni
2023-11-02Update raylib version to **raylib 5.0**Ray
2023-11-02Remove unneeded line on web platformRay
2023-11-02Support OpenGL ES 3.0 building on WebRay
For some reason, the equivalent requested context (WebGL 2.0) is not provided, despite being properly requested.
2023-11-02Comments tweaksRay
2023-11-02Update rprand.hRay
2023-11-02Partial fix the gesture system for DRM (#3502)ubkp
2023-11-02build.zig updates for 0.11.0 release. (#3501)Caleb Barger
2023-11-02[core] Fix gestures for `PLATFORM_DESKTOP_SDL` (#3499)ubkp
* Fix gestures for SDL * Review the gesture handling for SDL * Review 2
2023-11-02REVIEWED: Pointers exposing not required for ES3Ray
2023-11-01Update rcore_web.cRay
2023-11-01Update rcore_web.cRay
2023-11-01REVIEWED: Potential code issues reported by CodeQL #3476Ray
2023-11-01Moves keymapUS[] and fixes GetCharPressed for DRM (#3498)ubkp
2023-11-01Remove unused structures from lighting fragment shaders (#3497)Jeffery Myers
2023-11-01Update README.md (#3495)Techuuu
* Update README.md Fixed docs and improved. * Update README.md Done fixed it! * Update README.md Fixed!