Code Monkey home page Code Monkey logo

Comments (6)

anton-bondarev avatar anton-bondarev commented on September 23, 2024

@wawuwo Hi

I would like to make a contribution and I am willing to fix such issues for all shell scripts from said folder. Hence I wanted to ask if this kind of contribution will be of any value for the project?

Yes, sure.

from embox.

wawuwo avatar wawuwo commented on September 23, 2024

Sorry for the late reply, I saw your answer and since then I've been fixing the scripts in a forked repository.

I wanted to ask if there is a way to check that I haven't broken something accidentally? If there are typical usage scenarios I could check them myself. (I am striving to be careful but you never know until you check)

I found this git rebase upstream/master -i --exec make in contributing guide, is it still relevant?

from embox.

anton-bondarev avatar anton-bondarev commented on September 23, 2024

Sorry for the late reply

No problem!

I wanted to ask if there is a way to check that I haven't broken something accidentally? If there are typical usage scenarios I could check them myself. (I am striving to be careful but you never know until you check)

Unfortunataly for full checking you need apropriate boards. I have a couple of such boards. so let me check them when you create PR. I'll try to do it next week.

I found this git rebase upstream/master -i --exec make in contributing guide, is it still relevant?

Yes rebasing is actual (although '--exec make' looks wierd). Howeve you should do rebasing under upstream/master after your PR will be approved/

from embox.

wawuwo avatar wawuwo commented on September 23, 2024

@anton-bondarev I've finished and ready to open a pull request. But I can't decide if I should squash commits into more larger groups before PR. I intentionally made them as atomic as it reasonably possible to ease bisecting in case of any problems and ended up with 33 commits, mostly one commit per file… Would it be better if I squash them or it's OK to have 33 of them?

from embox.

anton-bondarev avatar anton-bondarev commented on September 23, 2024

@wawuwo

I've finished and ready to open a pull request.

Great. Do it!:)
You can make PR as is,and after aproving you will squash to one or several commits

from embox.

anton-bondarev avatar anton-bondarev commented on September 23, 2024

Closed by
#2847
#2857
#2863
#2876
#2878
#2879
#2880
#2882
#2884
#2885
#2887
#2888

from embox.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.