Software development
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 25/100
Research direction
The issue describes testing pull request #127 with GitHub Desktop, MATLAB's branch manager, and the GitLens extension, then asks whether posts like this are useful. Read the linked pull request and the repository's existing material to understand the intended format; done would require a decision about the post's value and a clear content task, which the issue does not specify.
Written by the indexing model from the issue text.
Description
Introduction: our goal as usual is to let you see how high level software development works and to let people who want to understand to have all the instruments.
Using
https://github.com/matlab/matlab-agentic-toolkit
people of MathWorks have done a pull request https://github.com/UniprJRC/FSDA/pull/127 to the FSDA codebase in order to increase the performance of some of our FSDA functions.
In order to test this pull request we execute the command
This creates a new brack called prova which contains the contents of the pull request
In GitHub Desktop I can see and manage the differences
or alternatively this can be done from the branch manager of MATLAB
Finallly, if you prefer to work with vscode this is what you get with the GITLENS extension
Please let me know if posts like this will be useful for the future or it is better to give up
- Dominant language
- MATLAB
- Stars
- 30
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from UniprJRC/DSwithMATLAB
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
UniprJRC/DSwithMATLAB#243 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
UniprJRC/DSwithMATLAB#242 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
UniprJRC/DSwithMATLAB#241 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
UniprJRC/DSwithMATLAB#240 ·
-
Suggestion for the next edition
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
UniprJRC/DSwithMATLAB#238 · 2 comments ·
All issues in UniprJRC/DSwithMATLAB
Similar issues
-
bug priority: p3 size: xs
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Ax/Atb trim the caller's GpuIds in place, so blocksize-1 solvers run on one GPU after the first anglePossibly taken @AnderBiguri claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
mathworks/MATLAB-Coding-Guidelines#7 · 3 comments ·